cve.bz

CVE-2014-2532 Incorrect Privilege Assignment

4.2 mediumEPSS 4.8%

Medium (4.2). EPSS 4.8% estimated probability of exploitation activity in the next 30 days.

On this page
sshd in OpenSSH before 6.6 does not properly support wildcards on AcceptEnv lines in sshd_config, which allows remote attackers to bypass intended environment restrictions by using a substring located before a wildcard character.

Severity

CVSS 3.1

4.2 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
4.8% (unchanged from 4.8% a week ago; 4.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 92nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-264 Permissions, Privileges, and Access Controls
CWE-20 Improper Input Validation
CWE-266 Incorrect Privilege Assignment
OWASP Top 10
A05:2025 Injection, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2014-2532 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2014-2532?via=ask-ai-copy and https://cve.bz/cve/CVE-2014-2532?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2014-2532 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
oracle:communications_user_data_repository10.0.1
openbsd:opensshthrough 6.5
openbsd:openssh6.0
openbsd:openssh6.1
openbsd:openssh6.2
openbsd:openssh6.3
openbsd:openssh6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian6.0openssh1:5.5p1-6+squeeze5DSA-2894-1
Debian7openssh1:6.0p1-4+deb7u1DSA-2894-1
Debian12, 13, 14openssh1:6.6p1-1DEBIAN-CVE-2014-2532
Red Hatenterprise_linux:6::client, enterprise_linux:6::computenode, enterprise_linux:6::server and 1 moreopenssh, openssh-ldap, openssh-server and 3 more0:5.3p1-104.el6RHSA-2014:1552
Red Hatenterprise_linux:6::client, enterprise_linux:6::computenode, enterprise_linux:6::server and 1 morepam_ssh_agent_auth0:0.9.3-104.el6RHSA-2014:1552

From the distributions' data via OSV.dev: the Debian Security Tracker; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Red Hat.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This issue affects the version of openssh as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6openssh-0:5.3p1-104.el6Fixed 2014-10-13RHSA-2014:1552
Red Hat Enterprise Linux 5opensshWill not fix
Red Hat Enterprise Linux 7opensshNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2014-2532.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON