CVE-2012-3525
UnknownEPSS 1.73%
Last modified
CVE-2012-3525 is a vulnerability of currently unknown severity. s2s/out.c in jabberd2 2.2.16 and earlier does not verify that a request was made for an XMPP Server Dialback response, which allows remote XMPP servers to spoof domains via a (1) Verify Response or (2) Authorization Response.. EPSS estimates a 1.73% chance of exploitation in the next 30 days.
Description
s2s/out.c in jabberd2 2.2.16 and earlier does not verify that a request was made for an XMPP Server Dialback response, which allows remote XMPP servers to spoof domains via a (1) Verify Response or (2) Authorization Response.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Jabber2 | Jabberd2 | 2.1.19 |
| Jabberd2 | Jabberd2 | <= 2.2.16 |
| Jabberd2 | Jabberd2 | 2.1 |
| Jabberd2 | Jabberd2 | 2.1.1 |
| Jabberd2 | Jabberd2 | 2.1.2 |
| Jabberd2 | Jabberd2 | 2.1.3 |
| Jabberd2 | Jabberd2 | 2.1.4 |
| Jabberd2 | Jabberd2 | 2.1.5 |
| Jabberd2 | Jabberd2 | 2.1.6 |
| Jabberd2 | Jabberd2 | 2.1.7 |
| Jabberd2 | Jabberd2 | 2.1.8 |
| Jabberd2 | Jabberd2 | 2.1.9 |
| Jabberd2 | Jabberd2 | 2.1.10 |
| Jabberd2 | Jabberd2 | 2.1.11 |
| Jabberd2 | Jabberd2 | 2.1.12 |
| Jabberd2 | Jabberd2 | 2.1.13 |
| Jabberd2 | Jabberd2 | 2.1.14 |
| Jabberd2 | Jabberd2 | 2.1.15 |
| Jabberd2 | Jabberd2 | 2.1.16 |
| Jabberd2 | Jabberd2 | 2.1.17 |
| Jabberd2 | Jabberd2 | 2.1.18 |
| Jabberd2 | Jabberd2 | 2.1.20 |
| Jabberd2 | Jabberd2 | 2.1.21 |
| Jabberd2 | Jabberd2 | 2.1.22 |
| Jabberd2 | Jabberd2 | 2.1.23 |
| Jabberd2 | Jabberd2 | 2.1.24 |
| Jabberd2 | Jabberd2 | 2.2.0 |
| Jabberd2 | Jabberd2 | 2.2.1 |
| Jabberd2 | Jabberd2 | 2.2.2 |
| Jabberd2 | Jabberd2 | 2.2.3 |
| Jabberd2 | Jabberd2 | 2.2.4 |
| Jabberd2 | Jabberd2 | 2.2.5 |
| Jabberd2 | Jabberd2 | 2.2.6 |
| Jabberd2 | Jabberd2 | 2.2.7 |
| Jabberd2 | Jabberd2 | 2.2.7.1 |
| Jabberd2 | Jabberd2 | 2.2.8 |
| Jabberd2 | Jabberd2 | 2.2.9 |
| Jabberd2 | Jabberd2 | 2.2.10 |
| Jabberd2 | Jabberd2 | 2.2.11 |
| Jabberd2 | Jabberd2 | 2.2.12 |
| Jabberd2 | Jabberd2 | 2.2.13 |
| Jabberd2 | Jabberd2 | 2.2.14 |
| Jabberd2 | Jabberd2 | 2.2.15 |
References
- http://secunia.com/advisories/50124Vendor Advisory
- http://xmpp.org/resources/security-notices/server-dialback/Vendor Advisory
- http://secunia.com/advisories/50124Vendor Advisory
- http://xmpp.org/resources/security-notices/server-dialback/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2012-3525?
s2s/out.c in jabberd2 2.2.16 and earlier does not verify that a request was made for an XMPP Server Dialback response, which allows remote XMPP servers to spoof domains via a (1) Verify Response or (2) Authorization Response.
How severe is CVE-2012-3525?
Severity scoring for CVE-2012-3525 is pending analysis. The EPSS model estimates a 1.73% probability of exploitation in the next 30 days.
How do I fix CVE-2012-3525?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2012-3525?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
