Deserialization of Untrusted Data in GitLab
- 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 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2
- 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
Summary
GitLab Enterprise Edition, a self-hosted software platform for source code management and DevOps, is affected by this flaw. An authenticated user with access to Duo Chat could potentially view Advanced Search configuration details and sensitive credentials.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup.
Timeline
- CVE published
- Record last updated
Affected versions
- GitLab GitLab
From 18.3 · fixed in 18.11.12; From 19.0 · fixed in 19.0.9; From 19.1 · fixed in 19.1.8; From 19.2 · fixed in 19.2.6; From 19.3 · fixed in 19.3.2