# CVE-2015-2914: Other in n/a

> Remote attackers can spoof DNS responses due to fixed source ports, potentially redirecting traffic for users of Securifi Almond devices.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 21 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qq45-89xg-7jpj

## What is CVE-2015-2914?

CVE-2015-2914 is a medium-severity vulnerability in n/a, published on 21 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Securifi Almond devices with firmware before AL1-R201EXP10-L304-W34 and Almond-2015 devices with firmware before AL2-R088M use a fixed source-port number in outbound DNS queries performed on behalf of any device, which makes it easier for remote attackers to spoof responses by using this number for the destination port, a different vulnerability than CVE-2015-7296.

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

It affects 2 products.


Products: Securifi Almond-2015 Firmware, Securifi Almond Firmware.

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

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

## Is CVE-2015-2914 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2915](https://insights.sbomify.com/CVE-2015-2915/): Hardcoded credentials in n/a (high 7.3)
- [CVE-2015-2916](https://insights.sbomify.com/CVE-2015-2916/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2015-2917](https://insights.sbomify.com/CVE-2015-2917/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2015-7296](https://insights.sbomify.com/CVE-2015-7296/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2914 is a medium-severity vulnerability in n/a, published on 21 Sep 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-2914 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-2914/ (Markdown: https://insights.sbomify.com/CVE-2015-2914/index.md)
```

## Sources

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

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