CVE-2012-3461

What it is

The (1) otrl_base64_otr_decode function in src/b64.c; (2) otrl_proto_data_read_flags and (3) otrl_proto_accept_data functions in src/proto.c; and (4) decode function in toolkit/parse.c in libotr before 3.2.1 allocates a zero-length buffer when decoding a base64 string, which allows remote attackers to cause a denial of service (application crash) via a message with the value "?OTR:===.", which triggers a heap-based buffer overflow.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

3.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2012-08-20 19:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:43 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 3.4% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2012-08-20 19:55 UTC

Last modified

2026-06-16 23:43 UTC

Exploit probability

3.4% · EPSS, next 30 days

Weakness

CWE-119 · Buffer errors

Record status

Modified

Affected

• Cypherpunks Libotr ≤ 3.2.0
• Cypherpunks Libotr 3.1.0

Attack profile CVSS 2.0 · 4.3

Attack vector

Network

Complexity

Medium

Authentication

None

Confidentiality

None

Integrity

None

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2012-3461.md and follow it. Check whether this project is affected by CVE-2012-3461. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge