Look up another CVE · open CVE-2020-0347 in the interactive tracker
CVE-2020-0347
In iptables, there is a possible out of bounds write due to an incorrect bounds check
The kernel CNA record carries no publication date. Subsystem unknown. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2020-0347 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | undetermined | 6.1.190-1 | Debian has not finished triaging this one for bookworm. |
| Debian 13trixie | undetermined | 6.12.113-1 | Debian has not finished triaging this one for trixie. |
| Debian 14forky | undetermined | 7.2.11-1 | Debian has not finished triaging this one for forky. |
| Debian unstablesid | undetermined | 7.2.11-1 | Debian has not finished triaging this one for sid. |
The vulnerability
What the bug is
In iptables, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-136658008
Where it lives
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.
Signals
- Published
- unknown
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.18%, higher than 7.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- unknown
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2020-0347, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.