ghsa-25v5-24mh-gcpq
Vulnerability from github
Published
2022-05-14 03:30
Modified
2022-05-14 03:30
Severity ?
5.9 (Medium) - CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Details

statem/statem_dtls.c in the DTLS implementation in OpenSSL 1.1.0 before 1.1.0a allocates memory before checking for an excessive length, which might allow remote attackers to cause a denial of service (memory consumption) via crafted DTLS messages.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2016-6308",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2016-09-26T19:59:00Z",
      severity: "HIGH",
   },
   details: "statem/statem_dtls.c in the DTLS implementation in OpenSSL 1.1.0 before 1.1.0a allocates memory before checking for an excessive length, which might allow remote attackers to cause a denial of service (memory consumption) via crafted DTLS messages.",
   id: "GHSA-25v5-24mh-gcpq",
   modified: "2022-05-14T03:30:19Z",
   published: "2022-05-14T03:30:19Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2016-6308",
      },
      {
         type: "WEB",
         url: "https://bto.bluecoat.com/security-advisory/sa132",
      },
      {
         type: "WEB",
         url: "https://cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf",
      },
      {
         type: "WEB",
         url: "https://git.openssl.org/?p=openssl.git;a=commit;h=df6b5e29ffea2d5a3e08de92fb765fdb21c7a21e",
      },
      {
         type: "WEB",
         url: "https://www.openssl.org/news/secadv/20160922.txt",
      },
      {
         type: "WEB",
         url: "https://www.tenable.com/security/tns-2016-16",
      },
      {
         type: "WEB",
         url: "https://www.tenable.com/security/tns-2016-20",
      },
      {
         type: "WEB",
         url: "https://www.tenable.com/security/tns-2016-21",
      },
      {
         type: "WEB",
         url: "http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10759",
      },
      {
         type: "WEB",
         url: "http://www-01.ibm.com/support/docview.wss?uid=swg21995039",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/93151",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1036885",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



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.