How severe is CVE-2012-5783?

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

Which packages are affected by CVE-2012-5783?

CVE-2012-5783 affects the following packages: commons-httpclient:commons-httpclient (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-5783?

The records we use list no patched version of commons-httpclient:commons-httpclient for CVE-2012-5783. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

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

How do I mitigate CVE-2012-5783 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.

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

No public exploit code has been indexed for CVE-2012-5783 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-5783?

CVE-2012-5783 has an EPSS (Exploit Prediction Scoring System) score of 9.2%, placing it in the 95th 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-5783?

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

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

CVE-2012-5783 was published on November 4, 2012 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-5783 — commons-httpclient

CVE-2012-5783 is a CWE-295 vulnerability in commons-httpclient:commons-httpclient. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Improper Certificate Validation in Apache Commons HttpClient

Also known asGHSA-3832-9276-x7gf

Published

Nov 4, 2012

Updated

Apr 16, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

9.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕commons-httpclient:commons-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

Note that the Commons HttpClient project is end of life. It has been replaced by the Apache HttpComponents project in its HttpClient and HttpCore modules. CVE-2012-5783 has been patched in v4.0 of the Apache HttpComponents HttpClient module.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`commons-httpclient:commons-httpclient`	≥ 3.0	No fix

Affected Products

2 products · 4 configurations

Application

httpclientapache

1 version

3.1

ubuntu linuxcanonical

3 versions

12.0414.0415.04

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-httpclient:commons-httpclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of commons-httpclient:commons-httpclient for CVE-2012-5783. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.

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 HatModerate

Product	Fixed in	Advisory
JBEWP 5 for RHEL 5	`jakarta-commons-httpclient-1:3.1-2.1_patch_01.ep5.el5`	RHSA-2013:0682
JBoss Enterprise BRMS Platform 5.3	see advisory	RHSA-2013:1006
Red Hat Enterprise Linux 5	`jakarta-commons-httpclient-1:3.0-7jpp.2`	RHSA-2013:0270
Red Hat Fuse 7.12	see advisory	RHSA-2023:3954
Red Hat JBoss A-MQ 6.3	see advisory	RHSA-2017:0868
Red Hat JBoss Enterprise Application Platform 5.2	see advisory	RHSA-2013:0679
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`jakarta-commons-httpclient-1:3.1-2.1_patch_01.ep5.el5`	RHSA-2013:0680
Red Hat JBoss Operations Network 3.2	see advisory	RHSA-2013:1853

Frequently Asked Questions

Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not 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 an arbitrary valid certificate. Note that the Commons HttpClient project is [end of life](https://hc.apache.org/httpclient-legacy/). It has been replaced by the Apache HttpComponents project in its [HttpClient](https://hc.apache.org/httpcomponents-client-5.4.x/) and

O3 Security · Impact-Aware SCA

Is CVE-2012-5783 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works