# CVE-2014-3036: Auth bypass in n/a

> Remote attackers can bypass topology access restrictions and obtain sensitive information in IBM API Management when basic authentication is enabled.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/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:** 8 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wqcv-4fmp-436f

## What is CVE-2014-3036?

CVE-2014-3036 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Jun 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in IBM API Management 3.0.0.0, when basic authentication is used for APIs, allows remote attackers to bypass intended restrictions on topology access, and obtain sensitive information, via unknown vectors.

## Which versions are affected by CVE-2014-3036?

It affects 1 product.


Products: Ibm Api Management.

## How do I fix CVE-2014-3036?

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

## Is CVE-2014-3036 being exploited?

There is no known exploitation of CVE-2014-3036 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-2015-0149](https://insights.sbomify.com/CVE-2015-0149/): Missing authorization in n/a (medium 5.5)
- [CVE-2014-6172](https://insights.sbomify.com/CVE-2014-6172/): Information disclosure in n/a (medium 5.0)
- [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-2014-3036 and fix it if it is affected.

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

## Sources

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

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