Research / Finding
fix: reject certs with literal-IP CN and no SAN
F-AWS-S2N-TLS-IP-CN-001
Public snapshot: 26 Sep 2026. 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
fix: reject certs with literal-IP CN and no SAN
merged
details
- Finding IDs
- F-AWS-S2N-TLS-IP-CN-001
- Status
- merged
- Reported via
- security contact (email)
- Note
- separate public s2n-tls fix for the literal-IP CN and no SAN case. this is not the same public fix chain as F-AWS-LC-NAMECONSTRAINTS-001.
F-AWS-S2N-TLS-IP-CN-001: Verification failures. An IP literal is accepted through common-name hostname fallback. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-AWS-S2N-TLS-IP-CN-001
Security area (1seal assessment): Identity. The TLS verifier rejects an IP address supplied only through certificate common-name fallback without a SAN. Reviewed 21 Sep 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.