Skip to content
Fencer Intel
medium 6.9

CVE-2012-0883 json

envvars (aka envvars-std) in the Apache HTTP Server before 2.4.2 places a zero-length directory name in the LD_LIBRARY_PATH, which allows l…

published 2012-04-18 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0906

cvss
6.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

envvars (aka envvars-std) in the Apache HTTP Server before 2.4.2 places a zero-length directory name in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse DSO in the current working directory during execution of apachectl.

Patch / fix

  • apache http_server 2.2.23
  • httpd Azure Linux 3.0 2.4.2-1

azure linux advisories AZL-41033

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-0883 updated cvss 3.7

httpd: insecure handling of LD_LIBRARY_PATH in envvars

  • Red Hat JBoss Enterprise Web Server 1 httpd
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Enterprise Application Platform 6.0
    fixed: vendor fix RHSA-2012:1594
  • Red Hat Directory Server 8 httpd Red Hat Enterprise Linux 5 httpd Red Hat Enterprise Linux 6 httpd, mod_ssl, httpd-tools, httpd-manual
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.