{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11518 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11518 is a high-severity vulnerability in n/a, published on 30 May 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-11518 and fix it if it is affected.\n\nWhat it is: CVE-2018-11518 is a high-severity vulnerability in n/a, published on 30 May 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-11518 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-2018-11518/ (Markdown: https://insights.sbomify.com/CVE-2018-11518/index.md)","id":"CVE-2018-11518","markdown":"https://insights.sbomify.com/CVE-2018-11518/index.md","name":"CVE-2018-11518","record":{"aliases":["GHSA-vv3x-8gqc-m4c5"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"HCL IVR system","requires_auth":"none","summary":"Attackers can forge service activation requests on legacy HCL IVR systems by replaying predictable DTMF tones, bypassing intended verification mechanisms.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"legacy_ivr_firmware","vendor":"hcltech"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A vulnerability allows a phreaking attack on HCL legacy IVR systems that do not use VoIP. These IVR systems rely on various frequencies of audio signals; based on the frequency, certain commands and functions are processed. Since these frequencies are accepted within a phone call, an attacker can record these frequencies and use them for service activations. This is a request-forgery issue when the required series of DTMF signals for a service activation is predictable (e.g., the IVR system does not speak a nonce to the caller). In this case, the IVR system accepts an activation request from a less-secure channel (any loudspeaker in the caller's physical environment) without verifying that the request was intended (it matches a nonce sent over a more-secure channel to the caller's earpiece).","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":"Cross-site request forgery in n/a","id":"CVE-2018-11518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Yosoro 1.0.4 has stored XSS.","id":"CVE-2018-11522"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-11517"},"products":["n/a"],"published":"2018-05-30","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":"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 forge service activation requests on legacy HCL IVR systems by replaying predictable DTMF tones, bypassing intended verification mechanisms.","url":"https://insights.sbomify.com/CVE-2018-11518/"}