# CVE-2017-1000381: Information disclosure in n/a

> A crafted DNS response can cause the c-ares library to read memory outside the input buffer, potentially disclosing sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** Yes
- **Published:** 7 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-1000381, CLEANSTART-2026-AQ61858, CLEANSTART-2026-VM93629, DEBIAN-CVE-2017-1000381, DLA-998-1, GHSA-vjr3-54h8-whpv, MGASA-2017-0215, SUSE-SU-2017:1792-1, UBUNTU-CVE-2017-1000381, USN-3395-1

## What is CVE-2017-1000381?

CVE-2017-1000381 is a high-severity vulnerability in Nodejs Node.js, published on 7 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The c-ares function `ares_parse_naptr_reply()`, which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer if the passed in DNS response packet was crafted in a particular way.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-1000381?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libcares2` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.9.1-8.1 |
| `libcares2` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.9.1-8.1 |
| `libcares2` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.9.1-8.1 |
| `libcares2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.9.1-8.1 |
| `libcares2` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.9.1-8.1 |
| `libcares2` | SUSE:Linux Enterprise Workstation Extension 12 SP2 | All versions | 1.9.1-8.1 |

Products: C-Ares C-Ares, C-Ares Project C-Ares, Nodejs Node.js.

## How do I fix CVE-2017-1000381?

Apply the vendor's patch.

## Is CVE-2017-1000381 being exploited?

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

## Other vulnerabilities in Nodejs Node.js

- [CVE-2016-5180](https://insights.sbomify.com/CVE-2016-5180/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-62408](https://insights.sbomify.com/CVE-2025-62408/): c-ares has a Use After Free vulnerability when connection is cleaned up after error (medium 5.9)
- [CVE-2020-22217](https://insights.sbomify.com/CVE-2020-22217/): Memory corruption in n/a (medium 5.9)
- [CVE-2024-25629](https://insights.sbomify.com/CVE-2024-25629/): c-ares out of bounds read in ares__read_line() (medium 4.4)
- [CVE-2020-14354](https://insights.sbomify.com/CVE-2020-14354/): Use after free in c-ares (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000381 and fix it if it is affected.

What it is: CVE-2017-1000381 is a high-severity vulnerability in Nodejs Node.js, published on 7 Jul 2017. 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-2017-1000381 in the wild and no public exploit code.

Affected product: Nodejs Node.js. 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-2017-1000381/ (Markdown: https://insights.sbomify.com/CVE-2017-1000381/index.md)
```

## Sources

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

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