{
  "id": "cve-2025-69419",
  "title": "Out-of-bounds write in PKCS12_get_friendlyname UTF-8 conversion",
  "product": "OpenSSL",
  "ai_system": "AISLE autonomous analyzer (specific model/version not disclosed)",
  "organization": "AISLE",
  "summary": "A crafted PKCS#12 BMPString friendly name containing a non-ASCII code point can trigger a one-byte write before an allocated buffer through the public `PKCS12_get_friendlyname()` API. The vendor says `PKCS12_parse()` takes a different path and is not affected.",
  "ai_role": "AISLE’s January 26, 2026 article says its autonomous analyzer found all 12 CVEs in OpenSSL’s January coordinated release, and individually names this case. OpenSSL’s own vulnerability record credits the named Aisle Research finder(s) for CVE-2025-69419; OpenSSL’s January 27 security advisory gives the flaw and report chronology. The exact model and division of AI versus researcher analysis are not public. OpenSSL credits Stanislav Fort (Aisle Research) as finder; AISLE says its autonomous analyzer found all 12 cases. Exact human/AI division is not published.",
  "disclosure_date": "2026-01-27",
  "ai_attribution_date": "2026-01-26",
  "classification": "disclosure",
  "classification_note": "OpenSSL published the vendor advisory and released fixes on January 27, 2026. The AISLE public AI attribution article appeared January 26, one day before the public vendor disclosure. No claim of in-the-wild exploitation is made.",
  "cves": [
    "CVE-2025-69419"
  ],
  "source_url": "https://openssl-library.org/news/vulnerabilities/#CVE-2025-69419",
  "ai_source_url": "https://aisle.com/blog/aisle-discovered-12-out-of-12-openssl-vulnerabilities",
  "remediation": "fix documented",
  "remediation_note": "OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19 and 1.1.1ze (premium-support branch). See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.",
  "advisory_url": "https://openssl-library.org/news/secadv/20260127.txt",
  "checked_date": "2026-11-15",
  "cvss": [
    {
      "cve": "CVE-2025-69419",
      "version": "3.1",
      "score": 7.4,
      "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2025/69xxx/CVE-2025-69419.json",
      "source_name": "CISA-ADP (ADP; CVE Program record)",
      "checked_date": "2026-11-16"
    }
  ],
  "impacts": [
    {
      "cves": [
        "CVE-2025-69419"
      ],
      "consequences": [
        "denial of service"
      ],
      "conditions": "CNA description: Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously\ncrafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing\nnon-ASCII BMP code point can trigger a one byte write before the allocated\nbuffer.\n\nImpact summary: The out-of-bounds write can cause a memory corruption\nwhich can have various consequences including a Denial of Service.\n\nThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12\nBMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes,\nthe helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16\nsource byte count as the destination buffer capacity to UTF8_putc(). For BMP\ncode points above U+07FF, UTF-8 requires three bytes, but the forwarded\ncapacity can be just two bytes. UTF8_putc() then returns -1, and this negative\nvalue is added to the output length without validation, causing the\nlength to become negative. The subsequent trailing NUL byte is then written\nat a negative offset, causing write outside of heap allocated buffer.\n\nThe vulnerability is reachable via the public PKCS12_get_friendlyname() API\nwhen parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a\ndifferent code path that avoids this issue, PKCS12_get_friendlyname() directly\ninvokes the vulnerable function. Exploitation requires an attacker to provide\na malicious PKCS#12 file to be parsed by the application and the attacker\ncan just trigger a one zero byte write before the allocated buffer.\nFor that reason the issue was assessed as Low severity according to our\nSecurity Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.",
      "exploitation": "Exploitation in the wild is not established by the cited description.",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2025/69xxx/CVE-2025-69419.json",
      "checked_date": "2026-11-16"
    }
  ]
}
