ghsa-74xm-qj29-cq8p
Vulnerability from github
Published
2021-05-25 18:42
Modified
2024-05-20 19:56
Severity ?
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Summary
In github.com/pion/webrtc, failed DTLS certificate verification doesn't stop data channel communication
Details

Impact

Data channel communication was incorrectly allowed with users who have failed DTLS certificate verification.

This attack requires * Attacker knows the ICE password. * Only take place during PeerConnection handshake.

This attack can be detected by monitoring PeerConnectionState in all versions of Pion WebRTC.

Patches

Users should upgrade to v3.0.15.

The exact patch is https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e

Workarounds

Users should listen for when PeerConnectionState changes to PeerConnectionStateFailed. When it enters this state users should not continue using the PeerConnection.

For more information

If you have any questions or comments about this advisory: * Open an issue in https://github.com/pion/webrtc * Email us at team@pion.ly

Thank you to https://github.com/Gaukas for discovering this.

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/pion/webrtc/v3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.0.15"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2021-28681"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-05-21T21:29:41Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "### Impact\nData channel communication was incorrectly allowed with users who have failed DTLS certificate verification.\n\nThis attack requires \n* Attacker knows the ICE password. \n* Only take place during PeerConnection handshake.\n\nThis attack can be detected by monitoring `PeerConnectionState` in all versions of Pion WebRTC.\n\n### Patches\nUsers should upgrade to v3.0.15. \n\nThe exact patch is https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e\n\n### Workarounds\nUsers should listen for when `PeerConnectionState` changes to `PeerConnectionStateFailed`. When it enters this state users should not continue using the PeerConnection.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/pion/webrtc\n* Email us at [team@pion.ly](mailto:team@pion.ly)\n\nThank you to https://github.com/Gaukas for discovering this.",
  "id": "GHSA-74xm-qj29-cq8p",
  "modified": "2024-05-20T19:56:37Z",
  "published": "2021-05-25T18:42:42Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-28681"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pion/webrtc/issues/1708"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pion/webrtc/pull/1709"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/pion/webrtc"
    },
    {
      "type": "WEB",
      "url": "https://pkg.go.dev/vuln/GO-2021-0104"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "In github.com/pion/webrtc, failed DTLS certificate verification doesn\u0027t stop data channel communication"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.