Encryption-key manipulation via forged upload requests
Published Jul 1, 2024 · Updated Mar 18, 2025
CSRF in S/Notify for Jira before 4.0.2 allows remote attackers to replace or remove a user's S/MIME certificate or PGP key. The user-profile upload functionality accepts a forged state-changing request under the logged-in user's session, adding, replacing, or deleting key material. Exploitation requires the upload option to be enabled and a logged-in user to follow a malicious link or visit a malicious site; replacement material must match the user's email address, and successful tampering prevents that user from decrypting notifications.
Summary
What happened
CSRF in S/Notify for Jira before 4.0.2 allows remote attackers to replace or remove a user's S/MIME certificate or PGP key. The user-profile upload functionality accepts a forged state-changing request under the logged-in user's session, adding, replacing, or deleting key material. Exploitation requires the upload option to be enabled and a logged-in user to follow a malicious link or visit a malicious site; replacement material must match the user's email address, and successful tampering prevents that user from decrypting notifications.
The record
- CVE
- CVE-2024-23737
- Published
- Jul 1, 2024
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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