# CVE-2015-7910: Auth bypass in n/a

> Remote attackers can bypass access restrictions in Exemys Telemetry Web Server by ignoring HTTP Location headers and processing the response body.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q5jg-rmvf-mrxc

## What is CVE-2015-7910?

CVE-2015-7910 is a high-severity authentication bypass vulnerability in n/a, published on 19 Nov 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Exemys Telemetry Web Server relies on an HTTP Location header to indicate that a client is unauthorized, which allows remote attackers to bypass intended access restrictions by disregarding this header and processing the response body.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Exemys Telemetry Web Server.

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

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

## Is CVE-2015-7910 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7910 is a high-severity authentication bypass vulnerability in n/a, published on 19 Nov 2015. 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-2015-7910 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-7910/ (Markdown: https://insights.sbomify.com/CVE-2015-7910/index.md)
```

## Sources

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

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