Private issue ID disclosure via moved issue JSON
Published Jan 28, 2020 · Updated Aug 4, 2024
Information disclosure in GitLab CE/EE 8.14 and later allows remote authenticated users to learn a private issue's new internal ID. The original issue's JSON response exposes moved_to_id without checking whether the requester may read the destination issue in its private project. Any authenticated account that can request the original public issue can confirm the move and obtain the destination's internal identifier, but no destination content is exposed.
Summary
What happened
Information disclosure in GitLab CE/EE 8.14 and later allows remote authenticated users to learn a private issue's new internal ID. The original issue's JSON response exposes moved_to_id without checking whether the requester may read the destination issue in its private project. Any authenticated account that can request the original public issue can confirm the move and obtain the destination's internal identifier, but no destination content is exposed.
The record
- CVE
- CVE-2019-5465
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 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?
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.
Weakness, pattern, technique
Public exploit references
- Authenticated moved-issue JSON disclosure stepsproof 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