# CVE-2012-1009: Denial of service in n/a

> Remote attackers can crash the NetSarang Xlpd daemon via malformed LPD requests, causing service disruption.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r3wp-gfpm-rjg8

## What is CVE-2012-1009?

CVE-2012-1009 is a medium-severity denial of service vulnerability in n/a, published on 14 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NetSarang Xlpd 4 Build 0100 and NetSarang Xmanager Enterprise 4 Build 0186 allow remote attackers to cause a denial of service (daemon crash) via a malformed LPD request.

## Which versions are affected by CVE-2012-1009?

It affects 2 products.


Products: Netsarang Xlpd, Netsarang Xmanager Enterprise.

## How do I fix CVE-2012-1009?

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

## Is CVE-2012-1009 being exploited?

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

Public exploit code:

- NetSarang Xlpd Printer Daemon 4 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-33035](https://insights.sbomify.com/CVE-2022-33035/): Privilege escalation in n/a (high 7.8)
- [CVE-2022-27965](https://insights.sbomify.com/CVE-2022-27965/): Code injection in n/a (medium 6.5)
- [CVE-2006-0148](https://insights.sbomify.com/CVE-2006-0148/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1009 and fix it if it is affected.

What it is: CVE-2012-1009 is a medium-severity denial of service vulnerability in n/a, published on 14 Feb 2012. 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-2012-1009 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-2012-1009/ (Markdown: https://insights.sbomify.com/CVE-2012-1009/index.md)
```

## Sources

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

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