p PatchFirst

CVE-2026-48508

CVE-2026-48508 · Lemur: Authorization bypass in StrictRolePermission / AuthorityCreatorPermission

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

Lemur manages TLS certificate creation. Prior to 1.9.1, StrictRolePermission and AuthorityCreatorPermission in lemur/auth/permissions.py call flask_principal.Permission.__init__() with zero Need objects when ADMIN_ONLY_AUTHORITY_CREATION and LEMUR_STRICT_ROLE_ENFORCEMENT are unset because both flags default to False. Flask-Principal Permission.allows() returns True when self.needs is empty, so the .can() authorization gate permits every authenticated identity, including the read-only role. A read-only user can access POST /api/1/authorities, POST /api/1/certificates/upload, POST /api/1/pending_certificates//upload, POST /api/1/notifications, PUT or DELETE /api/1/notifications/, and POST /api/1/domains to create root Certificate Authorities, upload arbitrary certificates, create or edit notifications that reach an SSRF sink, and create domain entries. Explicitly setting either flag to False continues to opt into the permissive behavior. This issue is fixed in version 1.9.1.

CVSS 8.8 · Élevée · EPSS 0,3% · Correctif disponible

Publication
Mise à jour

Pile logicielle: python

Produits et versions concernés

  • lemur

    Versions du logiciel
    • < 1.9.1: Concernée

    Aucun correctif publié

  • lemur PyPI

    Versions du logiciel
    • 0.11.0
    • 0.2.1
    • 0.8.0
    • 0.8.1
    • 0.9.0
    • 1.0.0
    • 1.1.0
    • 1.2.0
    • 1.3.1
    • 1.3.2
    • 1.4.0
    • 1.5.0
    • 1.6.0
    • 1.7.0
    • 1.8.0
    • 1.8.1
    • 1.8.2
    • 1.9.0
    Plages de versions concernées
    • ECOSYSTEM: < 1.9.1

    Mettez à jour vers 1.9.1

Sources originales

Vérifiez votre serveur →