{"answers":{"affected":"3 open source packages ship an affected version, including gateone. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-19003 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-19003 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-19003 is a medium-severity vulnerability in n/a, published on 6 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-19003 and fix it if it is affected.\n\nWhat it is: CVE-2020-19003 is a medium-severity vulnerability in n/a, published on 6 Oct 2021. 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-2020-19003 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gateone (PyPI): affected all versions; no fix listed\n- gateone (PyPI): affected all versions up to 1.2.0; no fix listed\n- gateone (PyPI): affected all versions up to 1.2.0; no fix listed\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-2020-19003/ (Markdown: https://insights.sbomify.com/CVE-2020-19003/index.md)","id":"CVE-2020-19003","markdown":"https://insights.sbomify.com/CVE-2020-19003/index.md","name":"CVE-2020-19003","record":{"aliases":["GHSA-q6j2-g8qf-wvf7","PYSEC-2021-423"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Gate One terminal","requires_auth":"none","summary":"Attackers can bypass origin verification checks to connect to Gate One instances from unauthorized hosts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gate_one","vendor":"liftoffsoftware"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"An issue in Gate One 1.2.0 allows attackers to bypass to the verification check done by the origins list and connect to Gate One instances used by hosts not on the origins list.","ecosystems":["PyPI"],"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":"Verification check bypass in Gate One","id":"CVE-2020-19003","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-19005"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":[],"package":"gateone","purl":"pkg:pypi/gateone","source":"PYSEC-2021-423"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.2.0"],"package":"gateone","purl":null,"source":"GHSA-q6j2-g8qf-wvf7"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.2.0"],"package":"gateone","purl":"pkg:pypi/gateone","source":"GHSA-q6j2-g8qf-wvf7"}],"prev":{"headline":"Mezzanine Cross Site Scripting (XSS) vulnerability","id":"CVE-2020-19002"},"products":["n/a"],"published":"2021-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-04","vendors":["n/a"]},"summary":"Attackers can bypass origin verification checks to connect to Gate One instances from unauthorized hosts.","url":"https://insights.sbomify.com/CVE-2020-19003/"}