# CVE-2007-1354: Race condition in n/a

> Authenticated administrators can exploit a race condition in JMX Console to escalate privileges from Read to Write mode.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rgjj-xgcc-3j8h

## What is CVE-2007-1354?

CVE-2007-1354 is a medium-severity vulnerability in n/a, published on 27 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Access Control functionality (JMXOpsAccessControlFilter) in JMX Console in JBoss Application Server 4.0.2 and 4.0.5 before 20070416 uses a member variable to store the roles of the current user, which allows remote authenticated administrators to trigger a race condition and gain privileges by logging in during a session by a more privileged administrator, as demonstrated by privilege escalation from Read Mode to Write Mode.

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

It affects 1 product.


Products: Jboss Jboss Application Server.

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

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

## Is CVE-2007-1354 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1036](https://insights.sbomify.com/CVE-2007-1036/): Missing authorization in n/a (high 7.5)
- [CVE-2006-5750](https://insights.sbomify.com/CVE-2006-5750/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1354 is a medium-severity vulnerability in n/a, published on 27 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-1354 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-2007-1354/ (Markdown: https://insights.sbomify.com/CVE-2007-1354/index.md)
```

## Sources

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

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