How severe is CVE-2012-6153?

No CVSS score has been assigned to CVE-2012-6153 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-6153?

CVE-2012-6153 affects the following packages: org.apache.httpcomponents:httpclient (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-6153?

Update org.apache.httpcomponents:httpclient to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-6153 is resolved across your whole dependency graph.

How do I detect CVE-2012-6153 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.httpcomponents:httpclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-6153 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2012-6153?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-6153 can be triaged on real exposure rather than presence alone.

Is CVE-2012-6153 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-6153 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-6153?

CVE-2012-6153 has an EPSS (Exploit Prediction Scoring System) score of 5.8%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-6153?

CVE-2012-6153 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-6153 published, and has it been updated?

CVE-2012-6153 was published on September 4, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2012-6153 — httpclient

CVE-2012-6153 is a Improper Input Validation vulnerability in org.apache.httpcomponents:httpclient. A fix is available for org.apache.httpcomponents:httpclient — see the affected versions and patch details below.

Improper certificate validation in org.apache.httpcomponents:httpclient

Also known asGHSA-2x83-r56g-cv47

Published

Sep 4, 2014

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

5.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕org.apache.httpcomponents:httpclient

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

http/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before 4.2.3 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5783.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.httpcomponents:httpclient`	all versions	4.2.3`org.apache.httpcomponents:httpclient:4.2.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.httpcomponents:httpclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.httpcomponents:httpclient to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-6153 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-6153 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2012-6153. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/solutions/1165533 This issue affects the versions of HttpComponents Client and ModeShape Client as shipped with Red Hat JBoss Data Virtualization 6. However, this flaw is not known to be exploitable under any supported…

Product	Fixed in	Advisory
JBEWP 5 for RHEL 5	`jakarta-commons-httpclient-1:3.1-4_patch_02.ep5.el5`	RHSA-2014:1320
JBEWP 5 for RHEL 5	`apache-cxf-0:2.2.12-14.patch_09.ep5.el5`	RHSA-2014:1833
Red Hat Developer Toolset 2.1 for RHEL 6	`devtoolset-2-httpcomponents-client-0:4.2.1-6.el6`	RHSA-2014:1098
Red Hat JBoss BPMS 6.0	`jakarta-commons-httpclient`	RHSA-2014:1892
Red Hat JBoss BPMS 6.0	`httpclient`	RHSA-2015:0234
Red Hat JBoss BPMS 6.0	`cxf`	RHSA-2015:0851
Red Hat JBoss BRMS 6.0	`jakarta-commons-httpclient`	RHSA-2014:1891
Red Hat JBoss BRMS 6.0	`httpclient`	RHSA-2015:0235

Ubuntu

USN-2769-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-6153 in your dependencies?

O3 Security finds CVE-2012-6153 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works