# CVE-2015-0149: Missing authorization in n/a

> Authenticated users can access restricted APIs to read sensitive information or modify data due to improper access controls in the developer portal.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:P/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:** 18 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wc8v-8q22-5546

## What is CVE-2015-0149?

CVE-2015-0149 is a medium-severity missing authorization vulnerability in n/a, published on 18 Mar 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The developer portal in IBM API Management 3.0 before 3.0.4.1 does not properly restrict access to the public and private APIs, which allows remote authenticated users to obtain sensitive information or modify data via unspecified API calls.

Weakness: CWE-264

## Which versions are affected by CVE-2015-0149?

It affects 1 product.


Products: Ibm Api Management.

## How do I fix CVE-2015-0149?

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

## Is CVE-2015-0149 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0559](https://insights.sbomify.com/CVE-2013-0559/): Missing authorization in n/a (medium 6.4)
- [CVE-2014-6172](https://insights.sbomify.com/CVE-2014-6172/): Information disclosure in n/a (medium 5.0)
- [CVE-2014-3036](https://insights.sbomify.com/CVE-2014-3036/): Auth bypass in n/a (medium 4.3)
- [CVE-2014-6133](https://insights.sbomify.com/CVE-2014-6133/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0149 and fix it if it is affected.

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

## Sources

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

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