# CVE-2015-7510: Memory corruption in n/a

> A stack-based buffer overflow in systemd's nss-mymachines module allows attackers to execute arbitrary code or escalate privileges.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** Yes
- **Published:** 25 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-7510, GHSA-65cx-r47g-rqpv

## What is CVE-2015-7510?

CVE-2015-7510 is a critical memory corruption vulnerability in Systemd Project Systemd, published on 25 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the getpwnam and getgrnam functions of the NSS module nss-mymachines in systemd.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Systemd Project Systemd.

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

Apply the vendor's patch.

## Is CVE-2015-7510 being exploited?

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

## Other vulnerabilities in Systemd Project Systemd

- [CVE-2017-1000082](https://insights.sbomify.com/CVE-2017-1000082/): Privilege escalation in n/a (critical 9.8)
- [CVE-2016-10156](https://insights.sbomify.com/CVE-2016-10156/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-9445](https://insights.sbomify.com/CVE-2017-9445/): Memory corruption in n/a (high 7.5)
- [CVE-2017-9217](https://insights.sbomify.com/CVE-2017-9217/): Null dereference in n/a (high 7.5)
- [CVE-2026-40224](https://insights.sbomify.com/CVE-2026-40224/): Privilege escalation in systemd (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7510 is a critical memory corruption vulnerability in Systemd Project Systemd, published on 25 Sep 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-2015-7510 in the wild and no public exploit code.

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

## Sources

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

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