iText 7.1.17 PDF File ARCFOUREncryption.encryptARCFOUR denial of service ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in iText 7.1.17. Impacted is the function ARCFOUREncryption.encryptARCFOUR of the component PDF File Handler. This manipulation causes denial of service.
The identification of this vulnerability is CVE-2022-24198. It is possible to initiate the attack remotely. There is no exploit available.
The actual existence of this vulnerability is currently in question.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in iText 7.1.17 and classified as problematic. Affected by this vulnerability is the function ARCFOUREncryption.encryptARCFOUR of the component PDF File Handler. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
iText v7.1.17 was discovered to contain an out-of-bounds exception via the component ARCFOUREncryption.encryptARCFOUR, which allows attackers to cause a Denial of Service (DoS) via a crafted PDF file. NOTE: Vendor does not view this as a vulnerability and has not found it to be exploitable.
The weakness was shared 02/02/2022. The advisory is shared at github.com. This vulnerability is known as CVE-2022-24198 since 01/31/2022. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The real existence of this vulnerability is still doubted at the moment.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: Denial of serviceCWE: 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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
01/31/2022 🔍02/02/2022 🔍
02/02/2022 🔍
05/01/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2022-24198 (🔍)
GCVE (CVE): GCVE-0-2022-24198
GCVE (VulDB): GCVE-100-192109
Entry
Created: 02/02/2022 07:19Updated: 05/01/2025 20:52
Changes: 02/02/2022 07:19 (39), 02/04/2022 14:39 (1), 12/06/2023 12:15 (2), 02/22/2024 21:21 (2), 08/03/2024 10:01 (33), 05/01/2025 20:52 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.