web-webauthn-software-authenticator
Register and authenticate against a WebAuthn/FIDO2 relying party using a self-built SOFTWARE authenticator (no hardware key) when the RP requests attestation "none" (or otherwise doesn't verify attestation trust). Load when: a login is "WebAuthn/passkey/ FIDO2", endpoints like /webauthn/register|aut
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/web-webauthn-software-authenticatorScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettoac9328fc…da3ae50a
ac9328fc0944…f32eda3ae50a1 file · 2.4 KBScansioneBasso1 segnalazione
- Link a domini esterni
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-webauthn-software-authenticator@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
- The app authenticates with WebAuthn/FIDO2 (register + authenticate "ceremonies",
navigator.credentials.create/get, client bundles calling/register/begin,/register/finish,/auth/begin,/auth/finish). register/beginreturns creation options with"attestation":"none"(or the RP never validates the attestation certificate chain). None-attestation means the server does NOT check that a real hardware authenticator vouched for the key — so a key you generate in software is accepted.- You can start registration: either registration is open, or you can leak an
invite/enrollment token (see
tech-mongo-agg-facet-bypassand NoSQL-injection notes).
Why it works
WebAuthn security rests on the authenticator signing a server challenge with a private
key. With attestation:none, the server trusts whatever public key the client submits at
register/finish (no proof it came from a certified device). You therefore generate your
own keypair, register its public key, then at auth/finish sign the server's challenge
with the matching private key — a completely valid assertion, because it is your key.
Method (Python: cryptography + cbor2, one cookie session)
POST /register/begin {invite_token}→ options (challenge,rp.id,user.id,pubKeyCredParamsincl. -7 = ES256,attestation:"none").- Build the authenticator:
- EC P-256 keypair. COSE public key =
cbor2.dumps({1:2, 3:-7, -1:1, -2:x, -3:y})(kty EC2, alg ES256, crv P-256, x, y — each coord 32 bytes big-endian). authData = sha256(rp.id) + flags + signCount(4B) + attestedCredentialDatawhereflags = 0x45(UP|UV|AT) andattestedCredentialData = aaguid(16×00) + credIdLen(2B) + credId(random) + coseKey.attestationObject = cbor2.dumps({"fmt":"none","attStmt":{}, "authData":authData}).clientDataJSON = {"type":"webauthn.create","challenge":<opts.challenge as-is>, "origin":"http(s)://<rp host:port>","crossOrigin":false}.
- EC P-256 keypair. COSE public key =
POST /register/finishwith{id:b64u(credId), rawId:b64u(credId), type:"public-key", response:{clientDataJSON:b64u, attestationObject:b64u}}→ credential created.POST /auth/begin→ newchallenge.clientDataJSON = {"type":"webauthn.get","challenge":<achal>,"origin":<origin>}.authData = sha256(rp.id) + flags(0x05 UP|UV) + signCount.signature = privkey.sign(authData + sha256(clientDataJSON), ec.ECDSA(SHA256))(cryptography emits DER — exactly what ES256 assertions use).userHandle = b64u(<user.id bytes>)(needed for discoverable/resident-key flows).
POST /auth/finishwith those fields → authenticated session cookie. Use it to hit the app (dashboard/account) and grab the flag.
Tools
python3 with cryptography and cbor2 (both common). fido2 (python-fido2) has a
built-in software authenticator if you prefer a library. All base64 is base64url,
no padding. A ready reference implementation: aegis/exploit-dev/pwn.py.
Gotchas
- Origin/rpId must match what the server expects, including scheme and port
(
http://host:3000), andrp.idis the host WITHOUT the port.sha256(rp.id)uses the host only. challengeinclientDataJSONis the same base64url string the server sent (it's just re-encoding the same bytes) — don't double-decode/re-pad it.- Resident-key/usernameless flows:
auth/beginreturns emptyallowCredentials; you MUST send the correctuserHandleatauth/finish. - If the RP validates attestation for real (
"direct"/known AAGUIDs with trusted roots), this won't work — you'd need a genuine chain.none(or a lenient verifier) is the tell.
Verify success
register/finish returns 200/created and auth/finish returns 200 and sets an
authenticated session cookie that unlocks previously-redirected pages (e.g. /dashboard
stops 302-ing to /login).
Learned on
AEGIS lab, 2026-08 — leaked invite token via Mongo aggregation injection, then
registered a software P-256 authenticator (attestation "none") as operator op-2026-0042.
Full worked example in aegis/notes.md (§6) and aegis/exploit-dev/pwn.py.
File di questa versione
- SKILL.md4.8 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | ac9328fc | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Web e bug bounty
Vai alla categoria- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login