CVE-2019-20022 Null dereference in n/a
Medium 6.5
Published
Updated
Check this codebase for CVE-2019-20022 and fix it if it is affected.
What it is: CVE-2019-20022 is a medium-severity vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20022 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-20022/ (Markdown: https://insights.sbomify.com/CVE-2019-20022/index.md)
An attacker can cause a denial of service via an invalid memory address dereference in the libsixel image library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2019-20022?
CVE-2019-20022 is a medium-severity vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
An invalid memory address dereference was discovered in load_pnm in frompnm.c in libsixel before 1.8.3.
Weakness: CWE-672
Which versions are affected by CVE-2019-20022?
It affects 1 product.
Products include Saitoha Libsixel.
How do I fix CVE-2019-20022?
Upgrade to a fixed version.
Is CVE-2019-20022 being exploited?
There is no known exploitation of CVE-2019-20022 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2019-20022, GHSA-86j3-8qqw-575j, UBUNTU-CVE-2019-20022.