CVE-2019-19256 Information disclosure in n/a
Medium 5.3
Published
Updated
Check this codebase for CVE-2019-19256 and fix it if it is affected.
What it is: CVE-2019-19256 is a medium-severity vulnerability in Gitlab Gitlab, published on 3 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19256 in the wild and no public exploit code.
Affected product: Gitlab Gitlab. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2019-19256/ (Markdown: https://insights.sbomify.com/CVE-2019-19256/index.md)
An attacker can access unauthorized information due to incorrect access control in GitLab Enterprise Edition.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2019-19256?
CVE-2019-19256 is a medium-severity vulnerability in Gitlab Gitlab, published on 3 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
GitLab Enterprise Edition (EE) 12.2 and later through 12.5 has Incorrect Access Control.
Weakness: CWE-200
Which versions are affected by CVE-2019-19256?
It affects 1 product.
Products include Gitlab Gitlab.
How do I fix CVE-2019-19256?
No fix has been published for CVE-2019-19256 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-19256 being exploited?
There is no known exploitation of CVE-2019-19256 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as GHSA-vpx5-hq6c-gr3m.