{"api_version":"1","generated_at":"2026-04-23T01:32:22+00:00","cve":"CVE-2021-28681","urls":{"html":"https://cve.report/CVE-2021-28681","api":"https://cve.report/api/cve/CVE-2021-28681.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2021-28681","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2021-28681"},"summary":{"title":"CVE-2021-28681","description":"Pion WebRTC before 3.0.15 didn't properly tear down the DTLS Connection when certificate verification failed. The PeerConnectionState was set to failed, but a user could ignore that and continue to use the PeerConnection. )A WebRTC implementation shouldn't allow the user to continue if verification has failed.)","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2021-03-18 04:15:00","updated_at":"2021-03-25 13:45:00"},"problem_types":["CWE-863"],"metrics":[],"references":[{"url":"https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p","name":"https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p","refsource":"MISC","tags":[],"title":"Failed DTLS certificate verification doesn't stop data channel communication · Advisory · pion/webrtc · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://github.com/pion/webrtc/issues/1708","name":"https://github.com/pion/webrtc/issues/1708","refsource":"MISC","tags":[],"title":"DTLS Fingerprints in SDP Offer/Answer are not verified · Issue #1708 · pion/webrtc · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-28681","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-28681","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2021","cve_id":"28681","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"webrtc_project","cpe5":"webrtc","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2021-28681","qid":"982400","title":"Go (go) Security Update for github.com/pion/webrtc/v3 (GHSA-74xm-qj29-cq8p)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2021-28681","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":"Pion WebRTC before 3.0.15 didn't properly tear down the DTLS Connection when certificate verification failed. The PeerConnectionState was set to failed, but a user could ignore that and continue to use the PeerConnection. )A WebRTC implementation shouldn't allow the user to continue if verification has failed.)"}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://github.com/pion/webrtc/issues/1708","refsource":"MISC","name":"https://github.com/pion/webrtc/issues/1708"},{"refsource":"MISC","name":"https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p","url":"https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p"}]}},"nvd":{"publishedDate":"2021-03-18 04:15:00","lastModifiedDate":"2021-03-25 13:45:00","problem_types":["CWE-863"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"LOW","availabilityImpact":"NONE","baseScore":5.3,"baseSeverity":"MEDIUM"},"exploitabilityScore":3.9,"impactScore":1.4},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:N/I:P/A:N","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":5},"severity":"MEDIUM","exploitabilityScore":10,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:webrtc_project:webrtc:*:*:*:*:*:*:*:*","versionEndExcluding":"3.0.15","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2021","CveId":"28681","Ordinal":"203857","Title":"CVE-2021-28681","CVE":"CVE-2021-28681","Year":"2021"},"notes":[{"CveYear":"2021","CveId":"28681","Ordinal":"1","NoteData":"Pion WebRTC before 3.0.15 didn't properly tear down the DTLS Connection when certificate verification failed. The PeerConnectionState was set to failed, but a user could ignore that and continue to use the PeerConnection. )A WebRTC implementation shouldn't allow the user to continue if verification has failed.)","Type":"Description","Title":null},{"CveYear":"2021","CveId":"28681","Ordinal":"2","NoteData":"2021-03-17","Type":"Other","Title":"Published"},{"CveYear":"2021","CveId":"28681","Ordinal":"3","NoteData":"2021-03-18","Type":"Other","Title":"Modified"}]}}}