# CVE-2019-11360: Memory corruption in n/a

> A buffer overflow in iptables-restore allows attackers to crash the program or execute code via a crafted file, affecting Linux systems.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Jul 2019
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2019-11360, GHSA-g644-fvpx-hqm9

## What is CVE-2019-11360?

CVE-2019-11360 is a medium-severity memory corruption vulnerability in n/a, published on 12 Jul 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A buffer overflow in iptables-restore in netfilter iptables 1.8.2 allows an attacker to (at least) crash the program or potentially gain code execution via a specially crafted iptables-save file. This is related to add_param_to_argv in xshared.c.

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

## Which versions are affected by CVE-2019-11360?

It affects 1 product.


Products: Netfilter Iptables.

## How do I fix CVE-2019-11360?

Upgrade to a fixed version.

## Is CVE-2019-11360 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2663](https://insights.sbomify.com/CVE-2012-2663/): Security feature bypass in n/a (high 7.5)
- [CVE-2001-1388](https://insights.sbomify.com/CVE-2001-1388/): Misconfiguration in n/a (medium 5.0)
- [CVE-2001-1387](https://insights.sbomify.com/CVE-2001-1387/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11360 and fix it if it is affected.

What it is: CVE-2019-11360 is a medium-severity memory corruption vulnerability in n/a, published on 12 Jul 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-11360 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-2019-11360/ (Markdown: https://insights.sbomify.com/CVE-2019-11360/index.md)
```

## Sources

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

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