CVE-2012-3404: The vfprintf function in stdio-common/vfprintf.c in libc in GNU C Library (aka glibc) 2.12 and other versions does not properly calculate a…
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 83% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: glibc (Debian:12) 2.13-35; glibc (Red Hat:enterprise_linux:6::client) 0:2.12-1.80.el6_3.3; glibc-common (Red Hat:enterprise_linux:6::client) 0:2.12-1.80.el6_3.3.
Low priority for now. Upgrade to glibc (Debian:12) 2.13-35; glibc (Red Hat:enterprise_linux:6::client) 0:2.12-1.80.el6_3.3; glibc-common (Red Hat:enterprise_linux:6::client) 0:2.12-1.80.el6_3.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The vfprintf function in stdio-common/vfprintf.c in libc in GNU C Library (aka glibc) 2.12 and other versions does not properly calculate a buffer length, which allows context-dependent attackers to bypass the FORTIFY_SOURCE format-string protection mechanism and cause a denial of service (stack corruption and crash) via a format string that uses positional parameters and many format specifiers.
- Published
- Feb 10, 2014
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 83th percentile
- CWE
- CWE-189
Report tools
Action score
21
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnu | glibc | cpe:2.3:a:gnu:glibc |
| redhat | enterprise virtualization | cpe:2.3:a:redhat:enterprise_virtualization |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux10.04
- canonical ubuntu linux11.04
- canonical ubuntu linux11.10
- canonical ubuntu linux12.04
- canonical ubuntu linux8.04
- gnu glibc2.12
- redhat enterprise linux6.0
- redhat enterprise virtualization3.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | glibc | before 2.13-35 | 2.13-35 |
| Red Hat:enterprise_linux:6::client | glibc | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | glibc-common | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | glibc-debuginfo | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | glibc-debuginfo-common | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | glibc-devel | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | glibc-headers | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | glibc-static | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | glibc-utils | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::client | nscd | before 0:2.12-1.80.el6_3.3 | 0:2.12-1.80.el6_3.3 |
| Red Hat:enterprise_linux:6::hypervisor | rhev-hypervisor6 | before 0:6.3-20120815.0.el6_3 | 0:6.3-20120815.0.el6_3 |
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4911Glibc: buffer overflow in ld.so leading to privilege escalationKEV80Now
- CVE-2015-0235Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows…68This week
- CVE-2015-7547Multiple stack-based buffer overflows in the (1) send_dg and (2) send_vc functions in the libresolv library in the GNU C Library (aka glibc…60This week
Published before and after this one in the same product
- ← EarlierCVE-2013-4332Oct 9, 2013 · Multiple integer overflows in malloc/malloc.c in the GNU C Library (aka glibc or libc6) 2.18 and earlier allow context-dependent attackers…18Monitor
- ← EarlierCVE-2013-4458Dec 12, 2013 · Stack-based buffer overflow in the getaddrinfo function in sysdeps/posix/getaddrinfo.c in GNU C Library (aka glibc or libc6) 2.18 and…21Monitor
- Later →CVE-2012-3405Feb 10, 2014 · The vfprintf function in stdio-common/vfprintf.c in libc in GNU C Library (aka glibc) 2.14 and other versions does not properly calculate a…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:glibc | 2.13-35 · Debian:12 | Package registry (OSV) |
| red hat:glibc | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-common | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-debuginfo | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-debuginfo-common | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-devel | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-headers | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-static | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-utils | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:nscd | 0:2.12-1.80.el6_3.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:rhev-hypervisor6 | 0:6.3-20120815.0.el6_3 · Red Hat:enterprise_linux:6::hypervisor | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-189 · Numeric ErrorsCVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.