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

> Remote authenticated users can impersonate arbitrary users by manipulating message owner tags, leading to privilege escalation.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/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:** 8 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8hfp-x3gr-3rfw

## What is CVE-2014-5375?

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

### Official description

The server in Adaptive Computing Moab before 7.2.9 and 8 before 8.0.0 does not properly validate the message owner matches the submitting user, which allows remote authenticated users to impersonate arbitrary users via the UserId and Owner tags.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Adaptivecomputing Moab.

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

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

## Is CVE-2014-5375 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5300](https://insights.sbomify.com/CVE-2014-5300/): Auth bypass in n/a (medium 5.0)
- [CVE-2014-5376](https://insights.sbomify.com/CVE-2014-5376/): Auth bypass in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5375 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Oct 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-5375 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-5375/ (Markdown: https://insights.sbomify.com/CVE-2014-5375/index.md)
```

## Sources

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

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