# CVE-2009-0041: Information disclosure in n/a

> Remote attackers can enumerate valid usernames by observing differences in responses to failed IAX2 login attempts in Asterisk.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0041, GHSA-94hf-42cp-33m4

## What is CVE-2009-0041?

CVE-2009-0041 is a medium-severity vulnerability in n/a, published on 14 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IAX2 in Asterisk Open Source 1.2.x before 1.2.31, 1.4.x before 1.4.23-rc4, and 1.6.x before 1.6.0.3-rc2; Business Edition A.x.x, B.x.x before B.2.5.7, C.1.x.x before C.1.10.4, and C.2.x.x before C.2.1.2.1; and s800i 1.2.x before 1.3.0 responds differently to a failed login attempt depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2009-0041?

It affects 3 products.


Products: Asterisk Asterisk Business Edition, Asterisk Open Source, Asterisk S800i Appliance.

## How do I fix CVE-2009-0041?

Upgrade to a fixed version.

## Is CVE-2009-0041 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5558](https://insights.sbomify.com/CVE-2008-5558/): Denial of service in n/a (medium 4.3)
- [CVE-2008-2119](https://insights.sbomify.com/CVE-2008-2119/): Null dereference in n/a (medium 4.3)
- [CVE-2007-6430](https://insights.sbomify.com/CVE-2007-6430/): Auth bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0041 and fix it if it is affected.

What it is: CVE-2009-0041 is a medium-severity vulnerability in n/a, published on 14 Jan 2009. 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-2009-0041 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-2009-0041/ (Markdown: https://insights.sbomify.com/CVE-2009-0041/index.md)
```

## Sources

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

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