Skip to content
Fencer Intel
high 7.5

CVE-2012-1184 in the critical feed json

Stack-based buffer overflow in the ast_parse_digest function in main/utils.c in Asterisk 1.8.x before 1.8.10.1 and 10.x before 10.2.1 allow…

published 2012-09-18 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1213

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
16.4%
EPSS 16.4% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

Stack-based buffer overflow in the ast_parse_digest function in main/utils.c in Asterisk 1.8.x before 1.8.10.1 and 10.x before 10.2.1 allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a long string in an HTTP Digest Authentication header.

Patch / fix

  • asterisk Debian 14 1:1.8.10.0~dfsg-1

debian advisories DEBIAN-CVE-2012-1184

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-1184 updated cvss 7.5

asterisk: Stack-based buffer overflow by processing certain HTTP Digest Authentication headers (AST-2012-003)

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-18855)
  2. Published

Exploit prediction

16.39% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-18855 Asterisk - 'ast_parse_digest()' Stack Buffer Overflow (PoC) dos, 2012-03-15

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.