Skip to content

chore(security): publish the two advisories fixed in 0.8.0 #428

Closed

Description

@Bccorb

Why

Two security advisories were fixed in 0.8.0 (#227 and the WebAuthn challenge store) but never published. One is still a draft and the other was closed without publishing, so neither lists a patched version. Disclosing fixed vulnerabilities is part of being checkably secure, and adopters on old versions cannot tell they are affected.

What

  • Set the patched version (0.8.0) on both advisories and publish them, requesting CVEs
  • For the audit write advisory, state the posture that shipped: lockout has its own counter, a failed counter write is reported on /health/status rather than swallowed, and an unreadable count is treated as locked
  • Check the Session 2 advisory box on FIDO Functional Certification #155

Done when

Both advisories are published with a patched version and are visible on the repository's Security tab.

Activity

  1. added this to the v0.19 milestone on Oct 17, 2026
  2. added theissue type on Oct 17, 2026
  3. added
    P1Security work outside the FIDO2 track
    secureServes the most-secure promise
    v0.19Targets the v0.19 release
    on Oct 17, 2026
  4. Bccorb commented on Oct 17, 2026

    @Bccorb
    ContributorAuthor

    Both advisories are published with 0.8.0 as the patched version: GHSA-2r8w-h4h9-jw8p and GHSA-7f64-r335-j842.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Security work outside the FIDO2 tracksecureServes the most-secure promisev0.19Targets the v0.19 release

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions