# CVE-2015-10011: OpenDNS OpenResolve endpoints.py neutralization for logs

> Improper output neutralization in OpenResolve logs allows attackers to inject data, requiring a patch to fix.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-ch8j-q2rq-5c87

## What is CVE-2015-10011?

CVE-2015-10011 is a medium-severity vulnerability in OpenDNS OpenResolve, published on 2 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in OpenDNS OpenResolve. This affects an unknown part of the file resolverapi/endpoints.py. The manipulation leads to improper output neutralization for logs. The identifier of the patch is 9eba6ba5abd89d0e36a008921eb307fcef8c5311. It is recommended to apply a patch to fix this issue. The identifier VDB-217197 was assigned to this vulnerability.

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-117 (Improper Output Neutralization for Logs)

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

It affects 1 product.


Products: Cisco Openresolve.

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

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

## Is CVE-2015-10011 being exploited?

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

## Other vulnerabilities in OpenDNS OpenResolve

- [CVE-2015-10010](https://insights.sbomify.com/CVE-2015-10010/): OpenDNS OpenResolve API endpoints.py get cross site scripting (low 3.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-10011 is a medium-severity vulnerability in OpenDNS OpenResolve, published on 2 Jan 2023. 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-10011 in the wild and no public exploit code.

Affected product: OpenDNS OpenResolve. 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-10011/ (Markdown: https://insights.sbomify.com/CVE-2015-10011/index.md)
```

## Sources

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

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