# CVE-2012-5524: Security feature bypass in n/a

> Gajim XMPP client fails to properly verify SSL certificates, allowing remote attackers to perform man-in-the-middle attacks and spoof servers.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5524, GHSA-g8h3-j4r4-m45r

## What is CVE-2012-5524?

CVE-2012-5524 is a medium-severity vulnerability in n/a, published on 8 Feb 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The _ssl_verify_callback function in tls_nb.py in Gajim before 0.15.3 does not properly verify SSL certificates, which allows remote attackers to conduct man-in-the-middle (MITM) attacks and spoof servers via an arbitrary certificate from a trusted CA.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-5524?

It affects 1 product.


Products: Gajim Gajim.

## How do I fix CVE-2012-5524?

Upgrade to a fixed version.

## Is CVE-2012-5524 being exploited?

There is no known exploitation of CVE-2012-5524 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-41055](https://insights.sbomify.com/CVE-2021-41055/): Denial of service in n/a (high 7.5)
- [CVE-2012-2086](https://insights.sbomify.com/CVE-2012-2086/): SQL injection in n/a (high 7.5)
- [CVE-2012-2085](https://insights.sbomify.com/CVE-2012-2085/): Command injection in n/a (medium 6.8)
- [CVE-2015-8688](https://insights.sbomify.com/CVE-2015-8688/): Missing authorization in n/a (medium 5.4)
- [CVE-2022-39835](https://insights.sbomify.com/CVE-2022-39835/): Business logic in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5524 and fix it if it is affected.

What it is: CVE-2012-5524 is a medium-severity vulnerability in n/a, published on 8 Feb 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-5524 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-5524/ (Markdown: https://insights.sbomify.com/CVE-2012-5524/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-5524
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-5524
- OSV: https://osv.dev/vulnerability/CVE-2012-5524

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-5524/
Summaries are generated and may contain mistakes; the official description above is the record.