CVE-2012-3461: The (1) otrl_base64_otr_decode function in src/b64.c; (2) otrl_proto_data_read_flags and (3) otrl_proto_accept

Q: How do I fix CVE-2012-3461?

libotr: upgrade to newer than 3.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2012-3461 being exploited?

CVE-2012-3461 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2012-3461 affect?

CVE-2012-3461 affects libotr. Severity is medium (CVSS 4.3). 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 w

Q: How urgent is CVE-2012-3461?

Priority 37/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2012-3461 is a medium-severity flaw (CVSS 4.3) affecting libotr. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
EPSS exploit chance	3.4% (top 11%)
CISA exploited list	No
Weakness	CWE-119
Published	2012-08-20
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: cypherpunks

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2012-08-20 19:55 UTCPublished CVE record published
2026-06-16 23:43 UTCUpdated Record last modified

cypherpunks libotr UPGRADE

Affected: <= 3.2.0 · 3.1.0

Fixed in: newer than 3.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libotr || rpm -q libotr || libotr --version

2. UPGRADE to newer than 3.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libotr

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libotr

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2012-3461?

libotr: upgrade to newer than 3.2.0. Exact commands for each OS are on this page.

Is CVE-2012-3461 being exploited?

CVE-2012-3461 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2012-3461 affect?

CVE-2012-3461 affects libotr. Severity is medium (CVSS 4.3). 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 w

How urgent is CVE-2012-3461?

Priority 37/100. No elevated risk signals yet.

Related CVEs

CVE-2016-2851 CRITICAL 9.8 MITIGATE MITIGATE Integer overflow in proto.c in libotr before 4.1.1 on 64-bit platforms allows remote attackers to cause a deni

References

← Back to latest CVEs