Insertion of Sensitive Information into Log File in GitLab
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.6epss 0.5%
exploitation probability
0.5%top 61% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.1 that under certain conditions could have allowed a user to access sensitive information that had already been committed to a project, due to insufficient output filtering in Duo Workflows.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Affected products
GitLab · GitLabpublic PoCs found — 1
cve_referencehackerone.com/reports/3757762unverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.