CVE-2017-16419
What it is
An issue was discovered in Adobe Acrobat and Reader: 2017.012.20098 and earlier versions, 2017.011.30066 and earlier versions, 2015.006.30355 and earlier versions, and 11.0.22 and earlier versions. The issue is a stack exhaustion problem within the JavaScript API, where the computation does not correctly control the amount of recursion that can happen with respect to system resources.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of service disruption.
- Exploit odds
- 6.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 6.8% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 6.8% · EPSS, next 30 days
- Weakness
- CWE-674
- Record status
- Modified
Affected
- Adobe Acrobat ≤ 11.0.22
- Adobe Acrobat ≤ 17.011.30066
- Adobe Acrobat Dc ≤ 17.012.20098
- Adobe Acrobat Dc ≤ 15.006.30355
- Adobe Acrobat Reader ≤ 11.0.22
- Adobe Acrobat Reader ≤ 17.011.30066
- Adobe Acrobat Reader Dc ≤ 17.012.20098
- Adobe Acrobat Reader Dc ≤ 15.006.30355
Attack profile CVSS 3.0 · 6.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-16419.md and follow it. Check whether this project is affected by CVE-2017-16419. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
