Payload: Client uploads could overwrite S3 objects
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.90.0, 4.0.0-canary.34
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Payload is a free and open source headless content management system. In @payloadcms/storage-s3 versions before 3.90.0 and canary versions before 4.0.0-canary.34, an authenticated user can overwrite an existing S3 object belonging to another upload collection when client uploads are enabled for multiple collections sharing a bucket and useCompositePrefixes is false or unset. This bypasses the target collection's access controls and prior file validation. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- payloadcms payload
fixed in 3.90.0; From 4.0.0-canary.0 · fixed in 4.0.0-canary.34
- @payloadcms storage-s3
fixed in 3.90.0; From 4.0.0-canary.0 · fixed in 4.0.0-canary.34
- @payloadcms/storage-s3npm
fixed in 3.90.0
- @payloadcms/storage-s3npm
From 4.0.0-canary.0 · fixed in 4.0.0-canary.34