Invia #1041008: lanyulei ferry <= 1.0.0 JWT Empty Secret Authentication Bypassinformazioni

Titololanyulei ferry <= 1.0.0 JWT Empty Secret Authentication Bypass
Descrizioneferry 1.0.0 and earlier validate session tokens with a JWT signing key that is either empty or left at the hard-coded factory default. An unauthenticated attacker who knows the token layout can mint a token carrying "rolekey": "admin" and an arbitrary future exp; the server accepts it as a fully privileged session. The impact is amplified by the authorization design: the Casbin enforcer takes its subject directly from the rolekey claim inside the token and never re-reads the user's role from the database. Forging that one claim is therefore equivalent to holding the administrator role. Because the same empty/default key also works across independent deployments of the product, this is a product-level defect rather than a single-site misconfiguration, and it can be mass-exploited via a search-engine fingerprint
Fonte⚠️ https://github.com/liumiya63-arch/CVE/blob/main/ferry-CVE-en-20261018/CVE-ferry-jwt-auth-bypass.md
Utente
 liumiya (UID 102169)
Sottomissione18/10/2026 10:20 (25 giorni fa)
Moderazione12/11/2026 18:34 (25 days later)
StatoAccettato
Voce VulDB436447 [lanyulei ferry 1.0.0/1.0.0-beta.1 JWT Validation middleware/auth.go autenticazione debole]
Punti20

Do you want to use VulDB in your project?

Use the official API to access entries easily!