{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15578 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15578 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15578 is a medium-severity vulnerability in Gitlab Gitlab, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15578 and fix it if it is affected.\n\nWhat it is: CVE-2019-15578 is a medium-severity vulnerability in Gitlab Gitlab, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-15578 in the wild and no public exploit code.\n\nAffected product: Gitlab Gitlab. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-15578/ (Markdown: https://insights.sbomify.com/CVE-2019-15578/index.md)","id":"CVE-2019-15578","markdown":"https://insights.sbomify.com/CVE-2019-15578/index.md","name":"CVE-2019-15578","record":{"aliases":["GHSA-m5gx-r8rq-3635","UBUNTU-CVE-2019-15578"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitLab CE/EE","requires_auth":"none","summary":"Attackers can discover private project paths via unsubscribe links in emails, exposing sensitive project information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"gitlab","vendor":"gitlab"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An information disclosure exists in \u003c 12.3.2, \u003c 12.2.6, and \u003c 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE). The path of a private project, that used to be public, would be disclosed in the unsubscribe email link of issues and merge requests.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in GitLab CE/EE","id":"CVE-2019-15578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"gitlab:gitlab","products":["gitlab:gitlab"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in GitLab CE/EE","id":"CVE-2019-15579"},"packages":[],"prev":{"headline":"Information disclosure in GitLab CE/EE","id":"CVE-2019-15577"},"products":["GitLab CE/EE"],"published":"2020-01-28","related":[{"cvss_score":10,"headline":"GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound","id":"CVE-2026-97229","kev_date_added":"2026-10-29","published":"2026-10-13"},{"cvss_score":10,"headline":"GitLab Community Edition and Enterprise Edition Path Traversal","id":"CVE-2026-85706","kev_date_added":"2026-09-11","published":"2026-09-12"},{"cvss_score":10,"headline":"GitLab Community and Enterprise Editions Improper Access Control","id":"CVE-2023-7028","kev_date_added":"2024-05-01","published":"2024-01-12"},{"cvss_score":10,"headline":"GitLab Community and Enterprise Editions Remote Code Execution","id":"CVE-2021-22205","kev_date_added":"2021-11-03","published":"2021-04-23"},{"cvss_score":6.8,"headline":"GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)","id":"CVE-2021-39935","kev_date_added":"2026-02-03","published":"2021-12-13"},{"cvss_score":6.8,"headline":"GitLab Server-Side Request Forgery (SSRF)","id":"CVE-2021-22175","kev_date_added":"2026-02-18","published":"2021-06-11"},{"cvss_score":10,"headline":"Integer Overflow or Wraparound in GitLab","id":"CVE-2026-110264","kev_date_added":null,"published":"2026-10-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["GitLab"]},"summary":"Attackers can discover private project paths via unsubscribe links in emails, exposing sensitive project information.","url":"https://insights.sbomify.com/CVE-2019-15578/"}