# CVE-2008-1897: Denial of service in n/a

> Remote attackers can cause denial of service via traffic amplification in Asterisk when unauthenticated calls are enabled.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/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 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1897, DSA-1563-1, GHSA-653q-fj3p-cqrg

## What is CVE-2008-1897?

CVE-2008-1897 is a medium-severity denial of service vulnerability in n/a, published on 23 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2008-1897?

It affects 5 products.


Products: Asterisk Asterisk Appliance Developer Kit, Asterisk Asterisk Business Edition, Asterisk Asterisknow, Asterisk Open Source, Asterisk S800i.

## How do I fix CVE-2008-1897?

Upgrade to a fixed version.

## Is CVE-2008-1897 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3264](https://insights.sbomify.com/CVE-2008-3264/): Denial of service in n/a (high 7.8)
- [CVE-2008-1289](https://insights.sbomify.com/CVE-2008-1289/): Memory corruption in n/a (high 7.5)
- [CVE-2008-1923](https://insights.sbomify.com/CVE-2008-1923/): Denial of service in n/a (high 7.1)
- [CVE-2008-0095](https://insights.sbomify.com/CVE-2008-0095/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1897 and fix it if it is affected.

What it is: CVE-2008-1897 is a medium-severity denial of service vulnerability in n/a, published on 23 Apr 2008. 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-2008-1897 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-2008-1897/ (Markdown: https://insights.sbomify.com/CVE-2008-1897/index.md)
```

## Sources

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

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