File tampering via unrestricted upload PATCH
Published Apr 9, 2024 · Updated Sep 4, 2024
File integrity violation in PsiTransfer before 2.2.0 allows remote attackers to append arbitrary content to uploaded files via PATCH requests. The /files/:id upload endpoint accepts an unauthenticated PATCH body for a completed file and appends it without checking that the upload bucket is locked. An attacker must obtain a distribution's file identifier, and later downloaders can receive content altered with malicious or phishing material.
Summary
What happened
File integrity violation in PsiTransfer before 2.2.0 allows remote attackers to append arbitrary content to uploaded files via PATCH requests. The /files/:id upload endpoint accepts an unauthenticated PATCH body for a completed file and appends it without checking that the upload bucket is locked. An attacker must obtain a distribution's file identifier, and later downloaders can receive content altered with malicious or phishing material.
The record
- CVE
- CVE-2024-31454
- Published
- Apr 9, 2024
- Updated
- Sep 4, 2024
- Vendor
- psi-4ward
- Product
- PsiTransfer
- Classifications
- CWE-434, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2024CVE publishedPublication date reported by the CVE source.
- Sep 4, 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=0 <2.2.0
- Affected versionversion=< 2.2.0
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
- PATCH /files/{id} file-append proof of conceptproof of concept · demonstrated
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