# CVE-2011-4820: Missing authorization in n/a

> Remote attackers can modify other users' preferences by manipulating the UID parameter, bypassing security restrictions in IBM Rational Asset Manager.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 26 Aug 2020
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-29x2-p4f6-vfcw

## What is CVE-2011-4820?

CVE-2011-4820 is a medium-severity missing authorization vulnerability in n/a, published on 26 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Rational Asset Manager 7.5 could allow a remote attacker to bypass security restrictions. An attacker could exploit this vulnerability using the UID parameter to modify another user's preferences.

## Which versions are affected by CVE-2011-4820?

It affects 1 product.


Products: Ibm Rational Asset Manager.

## How do I fix CVE-2011-4820?

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

## Is CVE-2011-4820 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4708](https://insights.sbomify.com/CVE-2011-4708/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4820 and fix it if it is affected.

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

## Sources

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

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