Unsolicited email via unverified notification address
Published Jun 19, 2020 · Updated Aug 4, 2024
Improper authorization in GitLab before 12.9.8, 12.10.0 through 12.10.6, and 13.0.0 allows remote authenticated users to select an unverified email. The notification settings flow accepts a newly added address as the notification destination without first checking that its confirmation completed. An existing account is required; the flaw permits unsolicited GitLab notifications to reach an address the account holder has not proved they control.
Summary
What happened
Improper authorization in GitLab before 12.9.8, 12.10.0 through 12.10.6, and 13.0.0 allows remote authenticated users to select an unverified email. The notification settings flow accepts a newly added address as the notification destination without first checking that its confirmation completed. An existing account is required; the flaw permits unsolicited GitLab notifications to reach an address the account holder has not proved they control.
The record
- CVE
- CVE-2020-13276
- Published
- Jun 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 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=>=12.10, <12.10.7
- Affected versionversion=<12.9.8
- Affected versionversion=>=13.0, <13.0.1
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
- Notification email confirmation-bypass reproductionproof 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