Certificate replacement via forged profile upload
Published Jul 1, 2024 · Updated Aug 1, 2024
CSRF in S/Notify for Confluence 4.0.1 and earlier allows attackers to replace a user's encryption key through profile upload. The user-profile upload flow accepts a state-changing certificate or PGP-key request induced from a malicious link or site. A user must be logged in, upload functionality must be enabled, and a replacement key must match the user's email address; replacement prevents decryption of later notifications.
Summary
What happened
CSRF in S/Notify for Confluence 4.0.1 and earlier allows attackers to replace a user's encryption key through profile upload. The user-profile upload flow accepts a state-changing certificate or PGP-key request induced from a malicious link or site. A user must be logged in, upload functionality must be enabled, and a replacement key must match the user's email address; replacement prevents decryption of later notifications.
The record
- CVE
- CVE-2024-23736
- Published
- Jul 1, 2024
- Updated
- Aug 1, 2024
- Vendor
- Savignano Software Solutions
- Product
- S/Notify Email Encryption for Jira
- Classifications
- T1566.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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 <=4.0.1
What conditions does exploitation require?
What is affected?
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