CVE-2016-9393 The jpc_pi_nextrpcl function in jpc_t2cod.c in JasPer before 1.900.17 allows remote attackers to cause a denial of service (assertion failur
Medium 5.5
Published
Updated
Check this codebase for CVE-2016-9393 and fix it if it is affected.
What it is: CVE-2016-9393 is a medium-severity vulnerability in Jasper Project Jasper, published on 23 Mar 2017.
Exploitation: There is no known exploitation of CVE-2016-9393 in the wild and no public exploit code.
Affected product: Jasper Project Jasper. 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-2016-9393/ (Markdown: https://insights.sbomify.com/CVE-2016-9393/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2016-9393?
CVE-2016-9393 is a medium-severity vulnerability in Jasper Project Jasper, published on 23 Mar 2017.
Official description
The jpc_pi_nextrpcl function in jpc_t2cod.c in JasPer before 1.900.17 allows remote attackers to cause a denial of service (assertion failure) via a crafted file.
Which versions are affected by CVE-2016-9393?
It affects 1 product.
Products include Jasper Project Jasper.
How do I fix CVE-2016-9393?
Upgrade to a fixed version.
Is CVE-2016-9393 being exploited?
There is no known exploitation of CVE-2016-9393 in the wild and no public exploit code.
Other vulnerabilities in Jasper Project Jasper
Sources
Also known as GHSA-6jhf-6jfc-fjgh, UBUNTU-CVE-2016-9393.