{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16915 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16915 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16915 is a critical path traversal vulnerability in n/a, published on 26 Sep 2019. 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-16915 and fix it if it is affected.\n\nWhat it is: CVE-2019-16915 is a critical path traversal vulnerability in n/a, published on 26 Sep 2019. 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-16915 in the wild and no public exploit code.\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-16915/ (Markdown: https://insights.sbomify.com/CVE-2019-16915/index.md)","id":"CVE-2019-16915","markdown":"https://insights.sbomify.com/CVE-2019-16915/index.md","name":"CVE-2019-16915","record":{"aliases":["GHSA-34rj-f5pg-64rh"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"pfSense firewall","requires_auth":"none","summary":"Attackers can read or modify arbitrary files on pfSense firewalls via unsanitized input in the picture widget.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pfsense","vendor":"netgate"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue was discovered in pfSense through 2.4.4-p3. widgets/widgets/picture.widget.php uses the widgetkey parameter directly without sanitization (e.g., a basename call) for a pathname to file_get_contents or file_put_contents.","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":"Path traversal in n/a","id":"CVE-2019-16915","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-16916"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16914"},"products":["n/a"],"published":"2019-09-26","related":[{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2020-21487","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":9.3,"headline":"Cross-site scripting in n/a","id":"CVE-2024-46538","kev_date_added":null,"published":"2024-10-22"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-48123","kev_date_added":null,"published":"2023-12-06"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-42326","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-27253","kev_date_added":null,"published":"2023-03-17"},{"cvss_score":8.8,"headline":"Command injection in pfSense CE and pfSense Plus","id":"CVE-2022-24299","kev_date_added":null,"published":"2022-03-31"}],"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":["n/a"]},"summary":"Attackers can read or modify arbitrary files on pfSense firewalls via unsanitized input in the picture widget.","url":"https://insights.sbomify.com/CVE-2019-16915/"}