# CVE-2007-1419: Missing authorization in n/a

> Local users can access sensitive MBeans data by exploiting improper policy enforcement in the JMX RMI-IIOP API.

- **Severity:** Medium 4.3 (`AV:L/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vh8v-h2hp-7m6q

## What is CVE-2007-1419?

CVE-2007-1419 is a medium-severity missing authorization vulnerability in n/a, published on 12 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Java Management Extensions Remote API Remote Method Invocation over Internet Inter-ORB Protocol (JMX RMI-IIOP) API in Java Dynamic Management Kit 5.1 before 20070309 does not properly enforce the java.policy, which allows local users to obtain certain MBeans data access by operating a server application accessed by a privileged remote authenticated user.

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

It affects 1 product.


Products: Sun Java Dynamic Management Kit.

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

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

## Is CVE-2007-1419 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1419 is a medium-severity missing authorization vulnerability in n/a, published on 12 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-1419 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-1419/ (Markdown: https://insights.sbomify.com/CVE-2007-1419/index.md)
```

## Sources

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

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