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

> Remote attackers can execute administrative commands without authentication to modify data, read sensitive information, or cause denial of service.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ppwq-8qp3-j45p

## What is CVE-2011-0489?

CVE-2011-0489 is a high-severity missing authorization vulnerability in n/a, published on 18 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The server components in Objectivity/DB 10.0 do not require authentication for administrative commands, which allows remote attackers to modify data, obtain sensitive information, or cause a denial of service by sending requests over TCP to (1) the Lock Server or (2) the Advanced Multithreaded Server, as demonstrated by commands that are ordinarily sent by the (a) ookillls and (b) oostopams applications.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Objectivity Objectivity\/Db.

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

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

## Is CVE-2011-0489 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-0489 exists.

Public exploit code:

- Objectivity/DB - Lack of Authentication (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0489 is a high-severity missing authorization vulnerability in n/a, published on 18 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-0489 exists.

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-0489/ (Markdown: https://insights.sbomify.com/CVE-2011-0489/index.md)
```

## Sources

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

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