# CVE-2017-1000363: Memory corruption in n/a

> An out-of-bounds write in the Linux kernel parallel port driver allows local attackers with bootloader control to execute arbitrary code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 13 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-1000363, GHSA-jg85-fhqf-2gfw, UBUNTU-CVE-2017-1000363

## What is CVE-2017-1000363?

CVE-2017-1000363 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 13 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Linux drivers/char/lp.c Out-of-Bounds Write. Due to a missing bounds check, and the fact that parport_ptr integer is static, a 'secure boot' kernel command line adversary (can happen due to bootloader vulns, e.g. Google Nexus 6's CVE-2016-10277, where due to a vulnerability the adversary has partial control over the command line) can overflow the parport_nr array in the following code, by appending many (>LP_NO) 'lp=none' arguments to the command line.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2017-1000363 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000363 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 13 Jul 2017. 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-2017-1000363 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-1000363/ (Markdown: https://insights.sbomify.com/CVE-2017-1000363/index.md)
```

## Sources

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

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