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

> Man-in-the-middle attackers can bypass authentication on CSL DualCom GPRS devices by spoofing responses, allowing unauthorized access to security systems.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pcrr-f2jc-hpgc

## What is CVE-2015-7285?

CVE-2015-7285 is a medium-severity authentication bypass vulnerability in n/a, published on 25 Nov 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CSL DualCom GPRS CS2300-R devices with firmware 1.25 through 3.53 do not require authentication from Alarm Receiving Center (ARC) servers, which allows man-in-the-middle attackers to bypass intended access restrictions via a spoofed HSxx response.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Csl Dualcom Gprs Cs2300-R Firmware.

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

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

## Is CVE-2015-7285 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7287](https://insights.sbomify.com/CVE-2015-7287/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2015-7286](https://insights.sbomify.com/CVE-2015-7286/): Weak cryptography in n/a (medium 6.4)
- [CVE-2015-7288](https://insights.sbomify.com/CVE-2015-7288/): Missing authorization in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7285 is a medium-severity authentication bypass vulnerability in n/a, published on 25 Nov 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7285 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-7285/ (Markdown: https://insights.sbomify.com/CVE-2015-7285/index.md)
```

## Sources

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

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