CVE-2012-5783

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 9%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
—
EG Score
0.0(none)
EPSS
94.8%
KEV
Not listed

Published

November 4, 2012

Last Modified

April 29, 2026

References (36)

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcommons-httpclient-java (3.1-10.2ubuntu0.15.04.1) @ vivid2026-05-29ubuntu
redhatpatch2023-06-29redhat
redhatpatch2017-04-03redhat
redhatredhat-support-plugin-rhev-0:3.3.0-14.el6ev2014-02-27redhat
redhatpatch2013-12-17redhat
redhatpatch2013-08-08redhat
redhatpatch2013-07-01redhat
redhatpatch2013-04-22redhat
redhatpatch2013-03-25redhat
redhatpatch2013-03-25redhat
redhatjakarta-commons-httpclient-1:3.1-2_patch_01.ep5.el62013-03-25redhat
redhatjakarta-commons-httpclient-1:3.1-0.7.el6_32013-02-19redhat
mavencommons-httpclient:commons-httpclient—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
commons-httpclient:commons-httpclient20020423 ... 3.1-rc1 (10 versions)——

Weakness Classification(1)

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

All Vendor Advisories

(13)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-05 11:29 UTCOSV refresh
  2. 2026-07-05 02:26 UTCEPSS rescore
  3. 2026-07-04 06:27 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-27 03:05 UTCEPSS rescore
  11. 2026-06-25 13:46 UTCEPSS rescore
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-23 21:30 UTCEPSS rescore
  15. 2026-06-22 14:22 UTCEPSS rescore
  16. 2026-06-22 14:22 UTCEPSS rescore
  17. 2026-06-21 14:53 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-21 01:56 UTCEPSS rescore
  20. 2026-06-19 19:23 UTCEPSS rescore
  21. 2026-06-19 19:22 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 49 more
  1. 2026-06-16 22:35 UTCOSV refresh
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-16 17:49 UTCEPSS rescore
  4. 2026-06-15 17:44 UTCEPSS rescore
  5. 2026-06-14 23:14 UTCEPSS rescore
  6. 2026-06-13 22:57 UTCEPSS rescore
  7. 2026-06-12 23:08 UTCEPSS rescore
  8. 2026-06-11 13:56 UTCEPSS rescore
  9. 2026-06-10 13:18 UTCEPSS rescore
  10. 2026-06-08 14:14 UTCEPSS rescore
  11. 2026-06-07 15:22 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-06 13:45 UTCEPSS rescore
  14. 2026-06-05 22:44 UTCEPSS rescore
  15. 2026-06-05 22:44 UTCEPSS rescore
  16. 2026-06-05 06:08 UTCEPSS rescore
  17. 2026-06-05 06:08 UTCEPSS rescore
  18. 2026-06-02 20:10 UTCEPSS rescore
  19. 2026-06-02 20:10 UTCEPSS rescore
  20. 2026-06-01 13:49 UTCEPSS rescore
  21. 2026-06-01 13:49 UTCEPSS rescore
  22. 2026-05-31 22:28 UTCEPSS rescore
  23. 2026-05-31 22:28 UTCEPSS rescore
  24. 2026-05-31 00:14 UTCEPSS rescore
  25. 2026-05-31 00:14 UTCEPSS rescore
  26. 2026-05-29 13:41 UTCEPSS rescore
  27. 2026-05-29 13:41 UTCEPSS rescore
  28. 2026-05-29 02:02 UTCEG score recompute
  29. 2026-05-29 02:02 UTCVendor advisory
  30. 2026-05-29 02:02 UTCGHSA enrichment
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-28 13:42 UTCEPSS rescore
  33. 2026-05-28 13:42 UTCEPSS rescore
  34. 2026-05-27 13:38 UTCEPSS rescore
  35. 2026-05-27 13:38 UTCEPSS rescore
  36. 2026-05-26 13:41 UTCEPSS rescore
  37. 2026-05-26 13:41 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-26 07:16 UTCEPSS rescore
  40. 2026-05-24 16:43 UTCEPSS rescore
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-22 21:15 UTCEPSS rescore
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-21 22:39 UTCEPSS rescore
  45. 2026-05-20 22:37 UTCEPSS rescore
  46. 2026-05-20 22:37 UTCEPSS rescore
  47. 2026-05-19 18:03 UTCOSV refresh
  48. 2026-05-18 21:29 UTCEPSS rescore
  49. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2012-5783?
CVE-2012-5783 is a none vulnerability published on November 4, 2012. 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…
When was CVE-2012-5783 disclosed?
CVE-2012-5783 was first published in the National Vulnerability Database on November 4, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-5783 actively exploited?
CVE-2012-5783 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2012-5783?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-5783, 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-5783

Explore →

Is Your Infrastructure Affected by CVE-2012-5783?

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

Start Free Scan →Browse All CVEs