ImpulseAdventure JPEGsnoop 1.7.5 JFIF Decoder divide by zero
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in ImpulseAdventure JPEGsnoop 1.7.5. This issue affects some unknown processing of the component JFIF Decoder. This manipulation causes divide by zero. This vulnerability is registered as CVE-2017-1000414. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in ImpulseAdventure JPEGsnoop 1.7.5. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component JFIF Decoder. The manipulation with an unknown input leads to a divide by zero vulnerability. The CWE definition for the vulnerability is CWE-369. The product divides a value by zero. As an impact it is known to affect availability. The summary by CVE is:
ImpulseAdventure JPEGsnoop version 1.7.5 is vulnerable to a division by zero in the JFIF decode handling resulting denial of service.
The bug was discovered 06/06/2017. The weakness was published 01/25/2018 (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2017-1000414 since 01/25/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 233 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.3
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Divide by zeroCWE: CWE-369 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
06/06/2017 🔍01/25/2018 🔍
01/25/2018 🔍
01/25/2018 🔍
01/26/2018 🔍
02/02/2023 🔍
Sources
Product: github.comAdvisory: b4e458612d4294e0cfe01dbf1c0b09a07a8133a4
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-1000414 (🔍)
GCVE (CVE): GCVE-0-2017-1000414
GCVE (VulDB): GCVE-100-112435
Entry
Created: 01/26/2018 07:53Updated: 02/02/2023 16:28
Changes: 01/26/2018 07:53 (56), 12/27/2019 16:02 (2), 02/02/2023 16:28 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.