CVE-2012-2132 json
libsoup 2.32.2 and earlier does not validate certificates or clear the trust flag when the ssl-ca-file does not exist, which allows remote…
published 2012-08-20 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2132
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
libsoup 2.32.2 and earlier does not validate certificates or clear the trust flag when the ssl-ca-file does not exist, which allows remote attackers to bypass authentication by connecting with a SSL connection.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-2132 updated cvss 5.8
libsoup: does not indicate whether or not an SSL certificate is valid
-
Red Hat Enterprise Linux 5 libsoup Red Hat Enterprise Linux 6 libsoupnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.55% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
openwall.com
/lists/oss-security/2012/04/24/13
mailing-list
-
securityfocus.com
/bid/53232
vdb-entry
-
openwall.com
/lists/oss-security/2012/04/24/3
mailing-list
-
openwall.com
/lists/oss-security/2012/04/30/7
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/75167
vdb-entry
-
openwall.com
/lists/oss-security/2012/05/02/8
mailing-list
- bugzilla.gnome.org /show_bug.cgi?id=666280
Sources
- CVE List CVE-2012-2132
- NVD CVE-2012-2132
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.