# CVE-2008-2019: Security feature bypass in n/a

> Remote attackers can bypass the audio CAPTCHA in Simple Machines Forum using automated Hamming distance analysis, allowing spam or abuse.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/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:** No
- **Published:** 30 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g6xp-5gpp-gjqv

## What is CVE-2008-2019?

CVE-2008-2019 is a high-severity vulnerability in n/a, published on 30 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Simple Machines Forum (SMF), probably 1.1.4, relies on "randomly generated static" to hinder brute-force attacks on the WAV file (aka audio) CAPTCHA, which allows remote attackers to pass the CAPTCHA test via an automated attack that considers Hamming distances.  NOTE: this issue reportedly exists because of an insufficient fix for CVE-2007-3308.

Weakness: CWE-264

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

It affects 1 product.


Products: Simple Machines Smf.

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

No fix has been published for CVE-2008-2019 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-2019 being exploited?

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

Public exploit code:

- https://github.com/TheRook/AudioCaptchaBypass-CVE-2008-2019 (github_poc): https://github.com/TheRook/AudioCaptchaBypass-CVE-2008-2019

## Other vulnerabilities in n/a

- [CVE-2006-6375](https://insights.sbomify.com/CVE-2006-6375/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2012-5903](https://insights.sbomify.com/CVE-2012-5903/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2004-1996](https://insights.sbomify.com/CVE-2004-1996/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2019 is a high-severity vulnerability in n/a, published on 30 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-2019 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-2019/ (Markdown: https://insights.sbomify.com/CVE-2008-2019/index.md)
```

## Sources

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

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