Is CVE-2012-6127 being actively exploited?

It is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no EPSS exploit-prediction score is available yet.

How do I fix CVE-2012-6127?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2012-6127 published?

CVE-2012-6127 was published on 2013-02-14 and last updated on 2023-11-07.

CVE-2012-6127

CVE-2012-6127 is a security vulnerability that is still awaiting full analysis and scoring.

Key facts

Actively exploited: Not listed in CISA KEV
Published: 2013-02-14
Last modified: 2023-11-07

Description

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This was originally reported as an issue in jakarta-commons-httpclient involving wildcard matching in the SSL hostname verifier, but further investigation showed that it was not a security issue. Notes: none

Frequently asked questions

What is CVE-2012-6127?: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This was originally reported as an issue in jakarta-commons-httpclient involving wildcard matching in the SSL hostname verifier, but further investigation showed that it was not a security issue. Notes: none
Is CVE-2012-6127 being actively exploited?: It is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no EPSS exploit-prediction score is available yet.
How do I fix CVE-2012-6127?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2012-6127 published?: CVE-2012-6127 was published on 2013-02-14 and last updated on 2023-11-07.