# CVE-2012-2148: Security feature bypass in AS

> Attackers can bypass Java security policies via property replacements in JBoss AS descriptors, potentially executing unauthorized actions.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 6 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fxg2-qg2r-vp8h

## What is CVE-2012-2148?

CVE-2012-2148 is a low-severity vulnerability in jbossas4 AS, published on 6 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue exists in the property replacements feature in any descriptor in JBoxx AS 7.1.1 ignores java security policies

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2012-2148?

It affects 2 products.


Products: Redhat Jboss Community Application Server, Redhat Jboss Enterprise Web Server.

## How do I fix CVE-2012-2148?

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

## Is CVE-2012-2148 being exploited?

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

## Other vulnerabilities in jbossas4 AS

- [CVE-2012-4529](https://insights.sbomify.com/CVE-2012-4529/): Information disclosure in n/a (medium 4.3)
- [CVE-2009-5066](https://insights.sbomify.com/CVE-2009-5066/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2148 and fix it if it is affected.

What it is: CVE-2012-2148 is a low-severity vulnerability in jbossas4 AS, published on 6 Dec 2019. 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-2012-2148 in the wild and no public exploit code.

Affected product: jbossas4 AS. 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-2012-2148/ (Markdown: https://insights.sbomify.com/CVE-2012-2148/index.md)
```

## Sources

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

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