# CVE-2010-2493: Missing authorization in n/a

> Remote attackers can bypass access restrictions in JBoss SOA Platform applications due to insecure default HTTP method configurations in deployment descriptors.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cc2j-r2rv-77c8

## What is CVE-2010-2493?

CVE-2010-2493 is a medium-severity missing authorization vulnerability in n/a, published on 9 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of the deployment descriptor (aka web.xml) in picketlink-sts.war in (1) the security_saml quickstart, (2) the webservice_proxy_security quickstart, (3) the web-console application, (4) the http-invoker application, (5) the gpd-deployer application, (6) the jbpm-console application, (7) the contract application, and (8) the uddi-console application in JBoss Enterprise SOA Platform before 5.0.2 contains GET and POST http-method elements, which allows remote attackers to bypass intended access restrictions via a crafted HTTP request.

Weakness: CWE-16

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

It affects 1 product.


Products: Redhat Jboss Enterprise Soa Platform.

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

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

## Is CVE-2010-2493 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2493 is a medium-severity missing authorization vulnerability in n/a, published on 9 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2493 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-2493/ (Markdown: https://insights.sbomify.com/CVE-2010-2493/index.md)
```

## Sources

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

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