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

> Remote authenticated users can bypass admin authentication to manage user accounts and read logs in Sybase M-Business Anywhere.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 8 Feb 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h3pp-99vq-4j5h

## What is CVE-2011-5078?

CVE-2011-5078 is a medium-severity missing authorization vulnerability in n/a, published on 8 Feb 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web administration interface in the server in Sybase M-Business Anywhere 6.7 before ESD# 3 and 7.0 before ESD# 7 does not require admin authentication for unspecified scripts, which allows remote authenticated users to list or delete user accounts, modify passwords, or read log files via HTTP requests, aka Bug IDs 678497 and 678499.

Weakness: CWE-264

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

It affects 1 product.


Products: Sybase M-Business Anywhere.

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

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

## Is CVE-2011-5078 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-5078 is a medium-severity missing authorization vulnerability in n/a, published on 8 Feb 2012. 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-5078 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-5078/ (Markdown: https://insights.sbomify.com/CVE-2011-5078/index.md)
```

## Sources

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

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