# CVE-2006-1827: Integer overflow in n/a

> Remote attackers can execute arbitrary code on Asterisk servers by exploiting an integer signedness error in JPEG processing.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 18 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1827, GHSA-3jff-hq38-gfvf

## What is CVE-2006-1827?

CVE-2006-1827 is a medium-severity vulnerability in Digium Asterisk, published on 18 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer signedness error in format_jpeg.c in Asterisk 1.2.6 and earlier allows remote attackers to execute arbitrary code via a length value that passes a length check as a negative number, but triggers a buffer overflow when it is used as an unsigned length.

## Which versions are affected by CVE-2006-1827?

It affects 1 product.


Products: Digium Asterisk.

## How do I fix CVE-2006-1827?

Upgrade to a fixed version.

## Is CVE-2006-1827 being exploited?

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

## Other vulnerabilities in Digium Asterisk

- [CVE-2017-14100](https://insights.sbomify.com/CVE-2017-14100/): Command injection in n/a (critical 9.8)
- [CVE-2014-8418](https://insights.sbomify.com/CVE-2014-8418/): Privilege escalation in n/a (critical 9.0)
- [CVE-2011-1599](https://insights.sbomify.com/CVE-2011-1599/): Missing authorization in n/a (critical 9.0)
- [CVE-2017-16671](https://insights.sbomify.com/CVE-2017-16671/): Memory corruption in n/a (high 8.8)
- [CVE-2017-7617](https://insights.sbomify.com/CVE-2017-7617/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1827 and fix it if it is affected.

What it is: CVE-2006-1827 is a medium-severity vulnerability in Digium Asterisk, published on 18 Apr 2006. 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-2006-1827 in the wild and no public exploit code.

Affected product: Digium Asterisk. 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-2006-1827/ (Markdown: https://insights.sbomify.com/CVE-2006-1827/index.md)
```

## Sources

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

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