# CVE-2009-1807: Code injection in n/a

> Remote attackers can execute arbitrary code via the SetAttributeValue method in Baofeng products, requiring immediate patching.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wqjm-mw67-qghq

## What is CVE-2009-1807?

CVE-2009-1807 is a critical code injection vulnerability in n/a, published on 28 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in Config.dll in Baofeng products 3.09.04.17 and earlier allows remote attackers to execute arbitrary code by calling the SetAttributeValue method, as exploited in the wild in April and May 2009.

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

It affects 1 product.


Products: Baofeng Storm.

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

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

## Is CVE-2009-1807 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1807 exists.

Public exploit code:

- BaoFeng - 'config.dll' ActiveX Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2617](https://insights.sbomify.com/CVE-2009-2617/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-1612](https://insights.sbomify.com/CVE-2009-1612/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4943](https://insights.sbomify.com/CVE-2007-4943/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4816](https://insights.sbomify.com/CVE-2007-4816/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1807 is a critical code injection vulnerability in n/a, published on 28 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1807 exists.

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-1807/ (Markdown: https://insights.sbomify.com/CVE-2009-1807/index.md)
```

## Sources

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

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