Aperi'Solve: Uncontrolled resource consumption in PNG "repair" (PCRT): a sub-100-byte upload pins a worker CPU (DoS)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Zeecka | AperiSolve | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Zeecka | Aperisolve |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.304% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zeecka
Zeecka aperisolve |
|
| Vendors & Products |
Zeecka
Zeecka aperisolve |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Aperi'Solve is an open-source steganalysis web platform. Prior to 3.4.2, an unauthenticated user can submit a PNG to POST /upload, which reaches aperisolve/utils/png.py through analyze_image, PCRTAnalyzer, PNG.repair(), and check_idat(). A malformed IDAT chunk can make attacker-controlled length and newline data drive an unbounded combinations search in PNG._fix_dos2unix(), causing repeated CRC checks that occupy a worker and delay or block image analysis for other users. Per-IP upload limits and eventual job termination bound the denial of service, and the issue has no confidentiality or integrity impact. This issue is fixed in version 3.4.2. | |
| Title | Aperi'Solve: Uncontrolled resource consumption in PNG "repair" (PCRT): a sub-100-byte upload pins a worker CPU (DoS) | |
| Weaknesses | CWE-400 CWE-407 CWE-834 |
|
| References |
| |
| Metrics |
cvssV3_1
|