CVE-2018-11518 json
A vulnerability allows a phreaking attack on HCL legacy IVR systems that do not use VoIP.
published 2018-05-30 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-3547
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
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).
Exploit prediction
1.37% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
twitter.com
/mishradhiraj_/status/1001664440759091207
third-party-advisory
-
datarift.blogspot.com
/2018/05/CVE-2018-11518-abusing-ivr-systems.html
third-party-advisory
-
virgil-cj.blogspot.com
/2018/05/0day-legacy-ivr-lets-phreak.html
third-party-advisory
-
twitter.com
/mishradhiraj_/status/1001664204485652482
third-party-advisory
Sources
- CVE List CVE-2018-11518
- NVD CVE-2018-11518
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.