{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41580 exists.","fix":"No fix has been published for CVE-2023-41580 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41580 is a high-severity vulnerability in Phpipam Phpipam, published on 2 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41580 and fix it if it is affected.\n\nWhat it is: CVE-2023-41580 is a high-severity vulnerability in Phpipam Phpipam, published on 2 Oct 2023. 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-2023-41580 exists.\n\nAffected product: Phpipam Phpipam. 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-2023-41580/ (Markdown: https://insights.sbomify.com/CVE-2023-41580/index.md)","id":"CVE-2023-41580","markdown":"https://insights.sbomify.com/CVE-2023-41580/index.md","name":"CVE-2023-41580","record":{"aliases":["GHSA-w44p-h466-6wfq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IPAM web application","requires_auth":"none","summary":"Attackers can enumerate LDAP fields and access sensitive data via crafted requests in phpIPAM, requiring an upgrade to secure the application.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpipam","vendor":"phpipam"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","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-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Phpipam before v1.5.2 was discovered to contain a LDAP injection vulnerability via the dname parameter at /users/ad-search-result.php. This vulnerability allows attackers to enumerate arbitrary fields in the LDAP server and access sensitive data via a crafted POST request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Other in n/a","id":"CVE-2023-41580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"phpipam:phpipam","products":["phpipam:phpipam"],"type":"other","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-41588"},"packages":[],"prev":{"headline":"Jeecg boot arbitrary file read vulnerability","id":"CVE-2023-41578"},"products":["n/a"],"published":"2023-10-02","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2022-41443","kev_date_added":null,"published":"2022-10-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16692","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16693","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16694","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16695","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16696","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-1000869","kev_date_added":null,"published":"2018-12-20"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-23","vendors":["n/a"]},"summary":"Attackers can enumerate LDAP fields and access sensitive data via crafted requests in phpIPAM, requiring an upgrade to secure the application.","url":"https://insights.sbomify.com/CVE-2023-41580/"}