# CVE-2015-6970: XML external entity in n/a

> Remote attackers can exploit XML injection in the camera's web interface to execute code or read sensitive data.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hw3j-wm48-xvw6

## What is CVE-2015-6970?

CVE-2015-6970 is a critical vulnerability in n/a, published on 18 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web interface in Bosch Security Systems NBN-498 Dinion2X Day/Night IP Cameras with H.264 Firmware 4.54.0026 allows remote attackers to conduct XML injection attacks via the idstring parameter to rcp.xml.

Weakness: CWE-91 (XML Injection)

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

It affects 1 product.


Products: Boschsecurity Nbn-498 Dinion2x Day\/Night Ip Cameras Firmware.

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

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

## Is CVE-2015-6970 being exploited?

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

Public exploit code:

- Bosch Security Systems Dinion NBN-498 - Web Interface XML Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6970 is a critical vulnerability in n/a, published on 18 Feb 2020. 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-6970 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-6970/ (Markdown: https://insights.sbomify.com/CVE-2015-6970/index.md)
```

## Sources

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

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