CVE-2017-5501: Integer Overflow
First published: Wed Mar 01 2017(Updated: )
Integer overflow in libjasper/jpc/jpc_tsfb.c in JasPer 1.900.17 allows remote attackers to cause a denial of service (crash) via a crafted file.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jasper Reports | =1.900.17 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-5501?
CVE-2017-5501 is considered to have a moderate severity due to its potential to cause denial of service attacks.
How do I fix CVE-2017-5501?
To fix CVE-2017-5501, update to a patched version of JasPer that resolves the integer overflow issue.
What types of attacks are possible due to CVE-2017-5501?
CVE-2017-5501 allows remote attackers to exploit integer overflow vulnerabilities, leading to application crashes.
Which versions of JasPer are affected by CVE-2017-5501?
CVE-2017-5501 specifically affects JasPer version 1.900.17.
Is it safe to use JasPer 1.900.17 after CVE-2017-5501?
Using JasPer 1.900.17 is not safe after CVE-2017-5501, as it may lead to system instability and potential downtime.
- agent/references
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- agent/weakness
- agent/severity
- agent/description
- agent/author
- agent/tags
- agent/softwarecombine
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/jasper project
- canonical/jasper reports
- version/jasper reports/1.900.17