{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2007-1822 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2007-1822 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-1822 is a critical authentication bypass vulnerability in n/a, published on 2 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2007-1822 and fix it if it is affected.\n\nWhat it is: CVE-2007-1822 is a critical authentication bypass vulnerability in n/a, published on 2 Apr 2007. 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-2007-1822 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-2007-1822/ (Markdown: https://insights.sbomify.com/CVE-2007-1822/index.md)","id":"CVE-2007-1822","markdown":"https://insights.sbomify.com/CVE-2007-1822/index.md","name":"CVE-2007-1822","record":{"aliases":["GHSA-65ph-7645-gxj3"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Voicemail system","requires_auth":"none","summary":"Remote attackers can access or modify voicemail messages and settings by spoofing Caller ID, bypassing authentication mechanisms.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"voice_mail_system","vendor":"alcatel-lucent"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Alcatel-Lucent Lucent Technologies voice mail systems allow remote attackers to retrieve or remove messages, or reconfigure mailboxes, by spoofing Calling Number Identification (CNID, aka Caller ID).","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-2007-1822","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2007"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2007-1823"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2007-1821"},"products":["n/a"],"published":"2007-04-02","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can access or modify voicemail messages and settings by spoofing Caller ID, bypassing authentication mechanisms.","url":"https://insights.sbomify.com/CVE-2007-1822/"}