{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3803 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3803 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3803 is a medium-severity vulnerability in Pivotal Concourse, published on 12 Jan 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-3803 and fix it if it is affected.\n\nWhat it is: CVE-2019-3803 is a medium-severity vulnerability in Pivotal Concourse, published on 12 Jan 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-3803 in the wild and no public exploit code.\n\nAffected product: Pivotal Concourse. 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-3803/ (Markdown: https://insights.sbomify.com/CVE-2019-3803/index.md)","id":"CVE-2019-3803","markdown":"https://insights.sbomify.com/CVE-2019-3803/index.md","name":"CVE-2019-3803","record":{"aliases":["GHSA-9xg8-22rr-c6vh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Concourse CI","requires_auth":"none","summary":"Attackers can steal user access tokens from browser history to impersonate users and access Concourse CI resources.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"concourse","vendor":"pivotal_software"}],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Pivotal Concourse, all versions prior to 4.2.2, puts the user access token in a url during the login flow. A remote attacker who gains access to a user's browser history could obtain the access token and use it to authenticate as the user.","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":"Concourse includes token in CLI authentication callback","id":"CVE-2019-3803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in cockpit","id":"CVE-2019-3804"},"packages":[],"prev":{"headline":"Additional information exposure with Spring Data JPA example matcher","id":"CVE-2019-3802"},"products":["Concourse"],"published":"2019-01-12","related":[{"cvss_score":10,"headline":"Concourse's GitLab auth allows impersonation","id":"CVE-2020-5415","kev_date_added":null,"published":"2020-08-12"},{"cvss_score":7.6,"headline":"Concourse Open Redirect in the /sky/login endpoint","id":"CVE-2020-5409","kev_date_added":null,"published":"2020-05-13"},{"cvss_score":7.6,"headline":"Pivotal Concourse allows malicious redirect urls on login","id":"CVE-2018-15798","kev_date_added":null,"published":"2018-12-19"},{"cvss_score":7.5,"headline":"Supply chain in Concourse CI: As of 2018-03-13, Pivotal does not believe that any resources or builds of Concourse have been compromised.","id":"CVE-2018-1227","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":6.8,"headline":"Concourse 5.0.0 SQL Injection vulnerability","id":"CVE-2019-3792","kev_date_added":null,"published":"2019-04-01"},{"cvss_score":5.4,"headline":"Team scope authorization bypass when Post/Put request with :team_name in body, allows HTTP parameter pollution","id":"CVE-2022-31683","kev_date_added":null,"published":"2022-12-19"}],"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-09-16","vendors":["Pivotal"]},"summary":"Attackers can steal user access tokens from browser history to impersonate users and access Concourse CI resources.","url":"https://insights.sbomify.com/CVE-2019-3803/"}