# CVE-2012-0864: Integer overflow in n/a > Integer overflow in glibc allows attackers to bypass FORTIFY_SOURCE and execute arbitrary code via format string attacks. - **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 May 2013 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-x2p4-f3vf-gwp3, RHSA-2012:0393, RHSA-2012:0397 ## What is CVE-2012-0864? CVE-2012-0864 is a medium-severity vulnerability in Gnu Glibc, published on 2 May 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Integer overflow in the vfprintf function in stdio-common/vfprintf.c in glibc 2.14 and other versions allows context-dependent attackers to bypass the FORTIFY_SOURCE protection mechanism, conduct format string attacks, and write to arbitrary memory via a large number of arguments. Weakness: CWE-189 ## Which versions are affected by CVE-2012-0864? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `glibc` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `glibc-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `glibc-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `glibc-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `glibc-headers` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `glibc-utils` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `nscd` | Red Hat:enterprise_linux:5::client | All versions | 0:2.5-81.el5_8.1 | | `glibc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `glibc-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `glibc-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `glibc-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `glibc-headers` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `glibc-utils` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `nscd` | Red Hat:enterprise_linux:5::server | All versions | 0:2.5-81.el5_8.1 | | `glibc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-common` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-headers` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-static` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-utils` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `nscd` | Red Hat:enterprise_linux:6::client | All versions | 0:2.12-1.47.el6_2.9 | | `glibc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-common` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-headers` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-static` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-utils` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `nscd` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.12-1.47.el6_2.9 | | `glibc` | Red Hat:enterprise_linux:6::server | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-common` | Red Hat:enterprise_linux:6::server | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:6::server | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.12-1.47.el6_2.9 | | `glibc-headers` | Red Hat:enterprise_linux:6::server | All versions | 0:2.12-1.47.el6_2.9 | Products: Gnu Glibc. ## How do I fix CVE-2012-0864? Apply the vendor's patch. ## Is CVE-2012-0864 being exploited? There is no known exploitation of CVE-2012-0864 in the wild and no public exploit code. ## Other vulnerabilities in Gnu Glibc - [CVE-2026-5450](https://insights.sbomify.com/CVE-2026-5450/): scanf %mc off-by-one heap buffer overflow (critical 9.8) - [CVE-2023-25139](https://insights.sbomify.com/CVE-2023-25139/): Memory corruption in n/a (critical 9.8) - [CVE-1999-0199](https://insights.sbomify.com/CVE-1999-0199/): Other in n/a (critical 9.8) - [CVE-2019-1010022](https://insights.sbomify.com/CVE-2019-1010022/): Security feature bypass in glibc (critical 9.8) - [CVE-2005-3590](https://insights.sbomify.com/CVE-2005-3590/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-0864 and fix it if it is affected. What it is: CVE-2012-0864 is a medium-severity vulnerability in Gnu Glibc, published on 2 May 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2012-0864 in the wild and no public exploit code. Affected product: Gnu Glibc. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2012-0864/ (Markdown: https://insights.sbomify.com/CVE-2012-0864/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-0864 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-0864 - OSV: https://osv.dev/vulnerability/CVE-2012-0864 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-0864/ Summaries are generated and may contain mistakes; the official description above is the record.