Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2014-8169

autofs: priv escalation via interpreter load path for program based automount maps

Overview

Published
18 Mar 2015
Modified
6 May 2026
Medium CVE
0 Registry packages
1 OS packages
5 Linux distributions
Yes Fix available

Description

automount 5.0.8, when a program map uses certain interpreted languages, uses the calling user's USER and HOME environment variable values instead of the values for the user used to run the mapped program, which allows local users to gain privileges via a Trojan horse program in the user home directory.

Source: OX vulnerability database

Severity

4.6 · MEDIUM

CVSS 2.0 base score, scored by redhat.

Access vector
Local
Access complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:L/AC:L/Au:N/C:P/I:P/A:P

Weakness: CWE-264

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

Oracle Linux 1 release · 1 package

fixed 1
autofs
Oracle Linux fixes for CVE-2014-8169
ReleasePackageFixed in
7 autofs 1:5.0.7-54.0.1.el7

Red Hat 1 release · 1 package

fixed 1
autofs
Red Hat fixes for CVE-2014-8169
ReleasePackageFixed inAdvisory
7 autofs 1:5.0.7-54.el7 RHSA-2015:2417

debian 4 releases · 1 package

fixed 4
autofs
debian fixes for CVE-2014-8169
ReleasePackageFixed in
11 autofs 5.0.8-2
12 autofs 5.0.8-2
13 autofs 5.0.8-2
14 autofs 5.0.8-2

echo 1 release · 1 package

fixed 1
autofs
echo fixes for CVE-2014-8169
ReleasePackageFixed in
autofs 5.0.8-2

openSUSE 1 release · 1 package

fixed 1
autofs
openSUSE fixes for CVE-2014-8169
ReleasePackageFixed inAdvisory
Tumbleweed autofs 5.1.1-3.5 openSUSE-SU-2024:10319-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.