Vulnerability-Lookup

GHSA-VV3X-8GQC-M4C5

Vulnerability from github – Published: 2022-05-14 03:12 – Updated: 2022-05-14 03:12

Details

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).

Severity

8.1 (High)


                  
                    CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2018-11518"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2018-05-30T20:29:00Z",
    "severity": "HIGH"
  },
  "details": "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\u0027s physical environment) without verifying that the request was intended (it matches a nonce sent over a more-secure channel to the caller\u0027s earpiece).",
  "id": "GHSA-vv3x-8gqc-m4c5",
  "modified": "2022-05-14T03:12:34Z",
  "published": "2022-05-14T03:12:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2018-11518"
    },
    {
      "type": "WEB",
      "url": "https://datarift.blogspot.com/2018/05/CVE-2018-11518-abusing-ivr-systems.html"
    },
    {
      "type": "WEB",
      "url": "https://twitter.com/mishradhiraj_/status/1001664204485652482"
    },
    {
      "type": "WEB",
      "url": "https://twitter.com/mishradhiraj_/status/1001664440759091207"
    },
    {
      "type": "WEB",
      "url": "http://virgil-cj.blogspot.com/2018/05/0day-legacy-ivr-lets-phreak.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2018-11518 (GCVE-0-2018-11518)

Vulnerability from cvelistv5 – Published: 2018-05-30 20:00 – Updated: 2024-08-05 08:10

Summary

Severity

No CVSS data available.

CWE

Assigner

mitre

References

4 references

URL	Tags
https://twitter.com/mishradhiraj_/status/10016644…	x_refsource_MISC
https://datarift.blogspot.com/2018/05/CVE-2018-11…	x_refsource_MISC
http://virgil-cj.blogspot.com/2018/05/0day-legacy…	x_refsource_MISC
https://twitter.com/mishradhiraj_/status/10016642…	x_refsource_MISC

Date Public

2018-05-30 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T08:10:14.610Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://twitter.com/mishradhiraj_/status/1001664440759091207"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://datarift.blogspot.com/2018/05/CVE-2018-11518-abusing-ivr-systems.html"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "http://virgil-cj.blogspot.com/2018/05/0day-legacy-ivr-lets-phreak.html"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://twitter.com/mishradhiraj_/status/1001664204485652482"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2018-05-30T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027s physical environment) without verifying that the request was intended (it matches a nonce sent over a more-secure channel to the caller\u0027s earpiece)."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2018-05-30T19:57:01.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://twitter.com/mishradhiraj_/status/1001664440759091207"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://datarift.blogspot.com/2018/05/CVE-2018-11518-abusing-ivr-systems.html"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "http://virgil-cj.blogspot.com/2018/05/0day-legacy-ivr-lets-phreak.html"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://twitter.com/mishradhiraj_/status/1001664204485652482"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2018-11518",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "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\u0027s physical environment) without verifying that the request was intended (it matches a nonce sent over a more-secure channel to the caller\u0027s earpiece)."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://twitter.com/mishradhiraj_/status/1001664440759091207",
              "refsource": "MISC",
              "url": "https://twitter.com/mishradhiraj_/status/1001664440759091207"
            },
            {
              "name": "https://datarift.blogspot.com/2018/05/CVE-2018-11518-abusing-ivr-systems.html",
              "refsource": "MISC",
              "url": "https://datarift.blogspot.com/2018/05/CVE-2018-11518-abusing-ivr-systems.html"
            },
            {
              "name": "http://virgil-cj.blogspot.com/2018/05/0day-legacy-ivr-lets-phreak.html",
              "refsource": "MISC",
              "url": "http://virgil-cj.blogspot.com/2018/05/0day-legacy-ivr-lets-phreak.html"
            },
            {
              "name": "https://twitter.com/mishradhiraj_/status/1001664204485652482",
              "refsource": "MISC",
              "url": "https://twitter.com/mishradhiraj_/status/1001664204485652482"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2018-11518",
    "datePublished": "2018-05-30T20:00:00.000Z",
    "dateReserved": "2018-05-28T00:00:00.000Z",
    "dateUpdated": "2024-08-05T08:10:14.610Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

GHSA-VV3X-8GQC-M4C5

CVE-2018-11518 (GCVE-0-2018-11518)

Tags

Sightings

Nomenclature