Skip to content
Noroxi
CVE-2008-1897· NVD / CVE Program· CNA mitre

The IAX2 channel driver (chan_iax2) in Asterisk Open Source 1.0.x, 1.2.x before 1.2.28, and 1.4.x before 1.4.19.1; Business Edition A.x.x, B

The IAX2 channel driver (chan_iax2) in Asterisk Open Source 1.0.x, 1.2.x before 1.2.28, and 1.4.x before 1.4.19.1; Business Edition A.x.x, B.x.x before B.2.5.2, and C.x.x before C.1.8.1; AsteriskNOW before 1.0.3; Appliance Developer Kit 0.x.x; and s800i before 1.1.0.3, when configured to allow unauthenticated calls, does not verify that an ACK response contains a call number matching the server's reply to a NEW message, which allows remote attackers to cause a denial of service (traffic amplification) via a spoofed ACK response that does not complete a 3-way handshake. NOTE: this issue exists because of an incomplete fix for CVE-2008-1923.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Apr 23, 2008
Updated
Jun 16, 2026
EPSS
2.7% · 86th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.7%

Affected systems

VendorProduct
asteriskasterisk appliance developer kit
asteriskasterisk business edition
asteriskasterisknow
asteriskopen source
asterisks800i

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • asterisk asterisk appliance developer kit0.2
  • asterisk asterisk appliance developer kit0.3
  • asterisk asterisk appliance developer kit0.4
  • asterisk asterisk appliance developer kit0.5
  • asterisk asterisk appliance developer kit0.6
  • asterisk asterisk appliance developer kit0.6.0
  • asterisk asterisk appliance developer kit0.7
  • asterisk asterisk appliance developer kit0.8
  • asterisk asterisk business editionup to b.2.5.1 inclusive
  • asterisk asterisk business editionup to c1.8.0 inclusive
  • asterisk asterisk business editiona
  • asterisk asterisk business editionb.1.3.2
  • asterisk asterisk business editionb.1.3.3
  • asterisk asterisk business editionb.2.2.0
  • asterisk asterisk business editionb.2.2.1
  • asterisk asterisk business editionb.2.3.1
  • asterisk asterisk business editionb.2.3.2
  • asterisk asterisk business editionb.2.3.3
  • asterisk asterisk business editionb.2.3.4
  • asterisk asterisk business editionb.2.3.6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:14asteriskbefore 1:1.4.19.1~dfsg-11:1.4.19.1~dfsg-1
Debian:4.0asteriskbefore 1:1.2.13~dfsg-2etch41:1.2.13~dfsg-2etch4

Same product

asterisk: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-1289Multiple buffer overflows in Asterisk Open Source 1.4.x before 1.4.18.1 and 1.4.19-rc3, Open Source 1.6.x before 1.6.0-beta6, Business Editi
    33Monitor
  • CVE-2008-1923The IAX2 channel driver (chan_iax2) in Asterisk 1.2 before revision 72630 and 1.4 before revision 65679, when configured to allow unauthenti
    28Monitor
  • CVE-2008-0095The SIP channel driver in Asterisk Open Source 1.4.x before 1.4.17, Business Edition before C.1.0-beta8, AsteriskNOW before beta7, Appliance
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:asterisk1:1.4.19.1~dfsg-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    none
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    None
    Availability impact
    P

    Weakness class (CWE)

    CWE-287 · Improper Authentication

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:N/A:P

    nvd-primary

    Root cause

    Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

    The bug in code

    The whole CWE-287 class

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

    Fixed

    ts
    const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records