Authenticated resource exhaustion via undeleted rejected uploads
Published Oct 19, 2021 · Updated Aug 3, 2024
Unrestricted upload in Firefly III before 5.6.2 allows remote authenticated users to retain rejected API uploads as temporary files. AttachmentHelper::saveAttachmentFromApi returns after rejecting a disallowed MIME type without closing the temporary resource, so the file is not deleted. Repeated rejected uploads consume temporary storage and can interrupt service; the published patch does not show persistence or execution of uploaded code.
Summary
What happened
Unrestricted upload in Firefly III before 5.6.2 allows remote authenticated users to retain rejected API uploads as temporary files. AttachmentHelper::saveAttachmentFromApi returns after rejecting a disallowed MIME type without closing the temporary resource, so the file is not deleted. Repeated rejected uploads consume temporary storage and can interrupt service; the published patch does not show persistence or execution of uploaded code.
The record
- CVE
- CVE-2021-3846
- Published
- Oct 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Firefly III
- Product
- Firefly III
- Classifications
- CWE-434, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <5.6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo