# CVE-2007-2429: Command injection in n/a

> Remote attackers can inject MySQL command-line arguments to gain administrative database access in ManageEngine PasswordManager Pro.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 2 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gf2r-m9f5-gm87

## What is CVE-2007-2429?

CVE-2007-2429 is a critical command injection vulnerability in n/a, published on 2 May 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ManageEngine PasswordManager Pro (PMP) allows remote attackers to obtain administrative access to a database by injecting a certain command line for the mysql program, as demonstrated by the "-port 2345" and "-u root" arguments.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2007-2429?

It affects 1 product.


Products: Manageengine Passwordmanager Pro.

## How do I fix CVE-2007-2429?

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

## Is CVE-2007-2429 being exploited?

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

Public exploit code:

- ManageEngine Password Manager Pro Build 5401 - Database Remote Unauthorized Access (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2429 and fix it if it is affected.

What it is: CVE-2007-2429 is a critical command injection vulnerability in n/a, published on 2 May 2007. 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-2007-2429 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-2007-2429/ (Markdown: https://insights.sbomify.com/CVE-2007-2429/index.md)
```

## Sources

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

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