{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-40530 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-40530 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-40530 is a high-severity authentication bypass vulnerability in n/a, published on 5 Aug 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-2024-40530 and fix it if it is affected.\n\nWhat it is: CVE-2024-40530 is a high-severity authentication bypass vulnerability in n/a, published on 5 Aug 2024. 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-2024-40530 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-2024-40530/ (Markdown: https://insights.sbomify.com/CVE-2024-40530/index.md)","id":"CVE-2024-40530","markdown":"https://insights.sbomify.com/CVE-2024-40530/index.md","name":"CVE-2024-40530","record":{"aliases":["GHSA-8x2c-hh3c-77q8"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Pantera CRM","requires_auth":"none","summary":"Attackers can bypass IP-based access controls in Pantera CRM by manipulating the X-Forwarded-For header, gaining unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"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:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"A vulnerability in Pantera CRM versions 401.152 and 402.072 allows unauthorized attackers to bypass IP-based access controls by manipulating the X-Forwarded-For header.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2024-40530","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2024-40531"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2024-40524"},"products":["n/a"],"published":"2024-08-05","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-24","vendors":["n/a"]},"summary":"Attackers can bypass IP-based access controls in Pantera CRM by manipulating the X-Forwarded-For header, gaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2024-40530/"}