1sealsemantic last-mile verification

Research / Finding

Related upstream change (DNS label boundary); the wildcard case of this finding is not shown fixed

F-LIBRESSL-NC-WILDCARD-001

Portfolio updated: 21 Oct 2026 (the last edit of this record set, not a re-check of every upstream source). Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
libressl/openbsdReported fixlibressl/openbsd

Related upstream change (DNS label boundary); the wildcard case of this finding is not shown fixed

fix mapping unconfirmed
details
Finding IDs
F-LIBRESSL-NC-WILDCARD-001
Status
fix mapping unconfirmed
Reported via
private security contact
Note
public OpenBSD/LibreSSL commit cf3eec32e7a6 (2026-04-13) fixes SAN dNSName name-constraint matching at the DNS label boundary: it replaces substring/suffix matching with exact DNSName constraint semantics and adds regression coverage. This finding concerns a wildcard name that covers an explicitly excluded concrete host. The commit leaves that wildcard case unchanged, so it does not confirm that this finding is fixed. LibreSSL releases that contain the commit (4.3.0/4.3.1; 4.3.1 release notes mention the SAN dNSName constraints fix; 4.3.2 stable) are evidence for the label-boundary change only. GHSA-h674-q4g3-3g47 was not publicly accessible at verification time. Status corrected 2026-10-10: an earlier version of this record presented the commit as the fix for this finding. Credit boundary (2026-10-13): the commit message says "Spotted by Haruto Kimura"; it names no report from 1seal. Whether this commit relates to a private 1seal report is unconfirmed, and an inaccessible GHSA is not evidence either way. This record asserts neither a confirmed association nor credit for 1seal.

F-LIBRESSL-NC-WILDCARD-001: Verification failures. A wildcard name can be accepted for a host that a name constraint excludes. The linked public commit addresses a different case (DNS label boundary matching), so no fix for this case is shown. Reviewed 10 Oct 2026. Mechanism assessed by 1seal.

Mechanism source for F-LIBRESSL-NC-WILDCARD-001

Security area (1seal assessment): Identity. A wildcard name can be accepted for a host that a name constraint excludes. The linked public commit addresses a different case (DNS label boundary matching), so no fix for this case is shown. Reviewed 10 Oct 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.

Paper copy does not update. Current version: 1seal.org/research/findings/F-LIBRESSL-NC-WILDCARD-001/