osec-2026-15
Vulnerability from osv_ocaml
Published
2026-08-07 13:00
Modified
2026-08-07 13:00
Summary
EC public key out of bounds read
Details

The internal Point.of_octets function is missing a length check for compressed points, and thus is raising an exception when a short buffer is provided. This affects all NIST curves (P-256, P-384, P-521) and both Dsa.pub_of_octets and Dh.key_exchange functions.

Fix

The fix is to check the length of the provided buffer.

Timeline

  • July 28th 2026: report to security@ocaml.org
  • August 7th: release of mirage-crypto-pk 2.3.0 and security advisory

{
  "affected": [
    {
      "ecosystem_specific": {
        "affected_bindings": [
          "Mirage_crypto_ec.P256.Dsa.pub_of_octets",
          "Mirage_crypto_ec.P256.Dh.key_exchange",
          "Mirage_crypto_ec.P384.Dsa.pub_of_octets",
          "Mirage_crypto_ec.P384.Dh.key_exchange",
          "Mirage_crypto_ec.P521.Dsa.pub_of_octets",
          "Mirage_crypto_ec.P521.Dh.key_exchange"
        ],
        "opam_constraint": "mirage-crypto-ec {\u003c \"2.3.0\"}"
      },
      "package": {
        "ecosystem": "opam",
        "name": "mirage-crypto-ec",
        "purl": "pkg:opam/mirage-crypto-ec"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.3.0"
            }
          ],
          "type": "ECOSYSTEM"
        },
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1f0bf67044e67cf6e46911fcd77a0ff706b6c3e7"
            }
          ],
          "repo": "https://github.com/mirage/mirage-crypto.git",
          "type": "GIT"
        }
      ],
      "versions": [
        "0.9.0",
        "0.9.1",
        "0.9.2",
        "0.10.0",
        "0.10.1",
        "0.10.2",
        "0.10.3",
        "0.10.4",
        "0.10.5",
        "0.10.6",
        "0.10.7",
        "0.11.0",
        "0.11.1",
        "0.11.2",
        "0.11.3",
        "1.0.0",
        "1.1.0",
        "1.2.0",
        "2.0.0",
        "2.0.1",
        "2.0.2",
        "2.0.3",
        "2.1.0",
        "2.2.0"
      ]
    }
  ],
  "credits": [
    {
      "name": "Thomas Gazagnaire",
      "type": "REPORTER"
    },
    {
      "name": "Hannes Mehnert",
      "type": "REMEDIATION_DEVELOPER"
    }
  ],
  "database_specific": {
    "cwe": [
      "CWE-125",
      "CWE-248"
    ],
    "human_link": "https://github.com/ocaml/security-advisories/tree/main/advisories/2026/OSEC-2026-15.md",
    "osv": "https://github.com/ocaml/security-advisories/tree/generated-osv/2026/OSEC-2026-15.json"
  },
  "details": "The internal Point.of_octets function is missing a length check for compressed\npoints, and thus is raising an exception when a short buffer is provided. This\naffects all NIST curves (P-256, P-384, P-521) and both `Dsa.pub_of_octets` and\n`Dh.key_exchange` functions.\n\n## Fix\n\nThe fix is to check the length of the provided buffer.\n\n## Timeline\n\n- July 28th 2026: report to security@ocaml.org\n- August 7th: release of mirage-crypto-pk 2.3.0 and security advisory",
  "id": "OSEC-2026-15",
  "modified": "2026-08-07T13:00:00Z",
  "published": "2026-08-07T13:00:00Z",
  "references": [],
  "schema_version": "1.7.4",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "EC public key out of bounds read"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…