# CVE-2010-2474: Privilege escalation in n/a

> Remote attackers can gain privileges by executing a service due to improper security domain consideration in JBoss ESB.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **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:** 9 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gq7m-hr2g-v7j8

## What is CVE-2010-2474?

CVE-2010-2474 is a low-severity vulnerability in n/a, published on 9 Aug 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JBoss Enterprise Service Bus (ESB) before 4.7 CP02 in JBoss Enterprise SOA Platform before 5.0.2 does not properly consider the security domain with which a service is secured, which might allow remote attackers to gain privileges by executing a service.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Redhat Jboss Enterprise Service Bus, Redhat Jboss Enterprise Soa Platform.

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

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

## Is CVE-2010-2474 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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