# CVE-2010-0103: Code injection in n/a

> A backdoor in Energizer DUO USB charger software allows remote attackers to download and execute arbitrary programs on Windows PCs via TCP port 7777.

- **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:** 9 Mar 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r443-h767-83gp

## What is CVE-2010-0103?

CVE-2010-0103 is a critical code injection vulnerability in n/a, published on 9 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UsbCharger.dll in the Energizer DUO USB battery charger software contains a backdoor that is implemented through the Arucer.dll file in the %WINDIR%\system32 directory, which allows remote attackers to download arbitrary programs onto a Windows PC, and execute these programs, via a request to TCP port 7777.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2010-0103?

It affects 1 product.


Products: Energizer Duo Usb.

## How do I fix CVE-2010-0103?

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

## Is CVE-2010-0103 being exploited?

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

Public exploit code:

- Energizer DUO USB Battery Charger Arucer.dll Trojan Code Execution (metasploit)
- Arugizer Trojan Horse (Energizer DUO) - Code Execution (Metasploit) (exploitdb)
- Energizer DUO Trojan Scanner (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0103 and fix it if it is affected.

What it is: CVE-2010-0103 is a critical code injection vulnerability in n/a, published on 9 Mar 2010. 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-2010-0103 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-2010-0103/ (Markdown: https://insights.sbomify.com/CVE-2010-0103/index.md)
```

## Sources

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

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