{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-6268 exists.","fix":"No fix has been published for CVE-2019-6268 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6268 is a high-severity path traversal vulnerability in n/a, published on 8 Mar 2024. 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-6268 and fix it if it is affected.\n\nWhat it is: CVE-2019-6268 is a high-severity path traversal vulnerability in n/a, published on 8 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-6268 exists.\n\nAffected product: n/a. 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-6268/ (Markdown: https://insights.sbomify.com/CVE-2019-6268/index.md)","id":"CVE-2019-6268","markdown":"https://insights.sbomify.com/CVE-2019-6268/index.md","name":"CVE-2019-6268","record":{"aliases":["GHSA-7h45-vv72-9v3p"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RAD SecFlow-2 device","requires_auth":"none","summary":"Attackers can read sensitive files like /etc/shadow via directory traversal in RAD SecFlow-2 devices.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-31","name":"Path Traversal: 'dir\\..\\..\\filename'"}],"description":"RAD SecFlow-2 devices with Hardware 0202, Firmware 4.1.01.63, and U-Boot 2010.12 allow URIs beginning with /.. for Directory Traversal, as demonstrated by reading /etc/shadow.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2019-6268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2019-6272"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-6267"},"products":["n/a"],"published":"2024-03-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can read sensitive files like /etc/shadow via directory traversal in RAD SecFlow-2 devices.","url":"https://insights.sbomify.com/CVE-2019-6268/"}