CVE-2012-6123

MEDIUMNVD 6.56.5—

6.5

Chicken before 4.8.0 does not properly handle NUL bytes in certain strings, which allows an attacker to conduct "poisoned NUL byte attack."

CVSS v3: 6.5
EG Score: 6.5(medium)
EPSS: 62.6%
KEV: Not listed

Published

October 31, 2019

Last Modified

November 21, 2024

References (6)

secalert@redhathttp://www.openwall.com/lists/oss-security/2013/02/08/2
secalert@redhathttps://access.redhat.com/security/cve/cve-2012-6123
secalert@redhathttps://security-tracker.debian.org/tracker/CVE-2012-6123
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2013/02/08/2
af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/security/cve/cve-2012-6123
af854a3a-2127-422b-91ae-364da2661108https://security-tracker.debian.org/tracker/CVE-2012-6123

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-20Improper Input Validation

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-06 13:45 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch

Frequently asked(5)

What is CVE-2012-6123?

CVE-2012-6123 is a medium vulnerability published on October 31, 2019. Chicken before 4.8.0 does not properly handle NUL bytes in certain strings, which allows an attacker to conduct "poisoned NUL byte attack."

When was CVE-2012-6123 disclosed?

CVE-2012-6123 was first published in the National Vulnerability Database on October 31, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2012-6123 actively exploited?

CVE-2012-6123 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 62.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2012-6123?

CVE-2012-6123 has a CVSS v3 base score of 6.5 (NVD).

How do I remediate CVE-2012-6123?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-6123, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2012-6123

Explore →

Is Your Infrastructure Affected by CVE-2012-6123?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2012-6123

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2012-6123?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)