{"answers":{"affected":"2 open source packages ship an affected version, including athlon1600/php-proxy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19246 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19246 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19246 is a high-severity path traversal vulnerability in n/a, published on 13 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19246 and fix it if it is affected.\n\nWhat it is: CVE-2018-19246 is a high-severity path traversal vulnerability in n/a, published on 13 Nov 2018. 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-2018-19246 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- athlon1600/php-proxy (Packagist): affected all versions up to 5.1.0; no fix listed\n- athlon1600/php-proxy (Packagist): affected all versions up to 5.1.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-2018-19246/ (Markdown: https://insights.sbomify.com/CVE-2018-19246/index.md)","id":"CVE-2018-19246","markdown":"https://insights.sbomify.com/CVE-2018-19246/index.md","name":"CVE-2018-19246","record":{"aliases":["GHSA-pc5h-m95g-v6rh"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP proxy library","requires_auth":"none","summary":"Remote attackers can read local files by exploiting hardcoded credentials in the default configuration of PHP-Proxy.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"php-proxy","vendor":"php-proxy"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"PHP-Proxy 5.1.0 allows remote attackers to read local files if the default \"pre-installed version\" (intended for users who lack shell access to their web server) is used. This occurs because the aeb067ca0aa9a3193dce3a7264c90187 app_key value from the default config.php is in place, and this value can be easily used to calculate the authorization data needed for local file inclusion.","ecosystems":["Packagist"],"exploits":{"exploitdb":1,"first_seen":"2018-11-15","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-07-20T13:06:26Z","kind":"github_poc","ref":"https://github.com/NeoWans/CVE-2018-19246","stars":1,"title":null},{"date":"2018-11-15","kind":"exploitdb","ref":"45861","stars":null,"title":"PHP-Proxy 5.1.0 - Local File Inclusion"}],"tier":"poc_unverified"},"has_fix":false,"headline":"LFI in PHP-Proxy 5.1.0","id":"CVE-2018-19246","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2018-19248"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["5.1.0"],"package":"athlon1600/php-proxy","purl":null,"source":"GHSA-pc5h-m95g-v6rh"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["5.1.0"],"package":"athlon1600/php-proxy","purl":"pkg:composer/athlon1600/php-proxy","source":"GHSA-pc5h-m95g-v6rh"}],"prev":{"headline":"XML external entity in n/a","id":"CVE-2018-19244"},"products":["n/a"],"published":"2018-11-13","related":[{"cvss_score":7.5,"headline":"Weak Cryptography in PHP-Proxy","id":"CVE-2018-19784","kev_date_added":null,"published":"2018-12-01"},{"cvss_score":7.5,"headline":"Unauthenticated File Read in PHP Proxy","id":"CVE-2018-19458","kev_date_added":null,"published":"2018-11-22"},{"cvss_score":6.1,"headline":"XSS in PHP-Proxy-App through v3.0","id":"CVE-2018-19785","kev_date_added":null,"published":"2018-12-01"}],"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":"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can read local files by exploiting hardcoded credentials in the default configuration of PHP-Proxy.","url":"https://insights.sbomify.com/CVE-2018-19246/"}