# CVE-2012-2369: Other in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in the Pidgin OTR plugin's logging function.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2369, DSA-2476-1, GHSA-qv74-54r8-p8x7

## What is CVE-2012-2369?

CVE-2012-2369 is a high-severity vulnerability in n/a, published on 23 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the log_message_cb function in otr-plugin.c in the Off-the-Record Messaging (OTR) pidgin-otr plugin before 3.2.1 for Pidgin might allow remote attackers to execute arbitrary code via format string specifiers in data that generates a log message.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Cypherpunks Pidgin-Otr.

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

Upgrade to a fixed version.

## Is CVE-2012-2369 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8833](https://insights.sbomify.com/CVE-2015-8833/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2369 is a high-severity vulnerability in n/a, published on 23 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2369 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-2369/ (Markdown: https://insights.sbomify.com/CVE-2012-2369/index.md)
```

## Sources

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

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