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

> Remote attackers can bypass authentication in IBM Security Access Manager via the Local Management Interface using invalid credentials.

- **Severity:** High 8.0 (`AV:A/AC:L/Au:N/C:C/I:P/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xqhf-qrgr-g45h

## What is CVE-2014-3053?

CVE-2014-3053 is a high-severity authentication bypass vulnerability in n/a, published on 21 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Local Management Interface (LMI) in IBM Security Access Manager (ISAM) for Mobile 8.0 with firmware 8.0.0.0 through 8.0.0.3 and IBM Security Access Manager for Web 7.0, and 8.0 with firmware 8.0.0.2 and 8.0.0.3, allows remote attackers to bypass authentication via a login action with invalid credentials.

Weakness: CWE-287 (Improper Authentication)

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

It affects 5 products.


Products: Ibm Security Access Manager for Mobile Appliance, Ibm Security Access Manager for Mobile Software, Ibm Security Access Manager for Web 8.0 Firmware, Ibm Security Access Manager for Web Appliance, Ibm Security Access Manager for Web Software.

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

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

## Is CVE-2014-3053 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3073](https://insights.sbomify.com/CVE-2014-3073/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3053 and fix it if it is affected.

What it is: CVE-2014-3053 is a high-severity authentication bypass vulnerability in n/a, published on 21 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3053 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-3053/ (Markdown: https://insights.sbomify.com/CVE-2014-3053/index.md)
```

## Sources

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

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