AnsibleForms: Authentication bypass via hard-coded default JWT signing secret
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ansibleguy76 | ansibleforms | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ansibleguy76 | Ansibleforms |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 2.0% (1.980% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ansibleguy76
Ansibleguy76 ansibleforms |
|
| Vendors & Products |
Ansibleguy76
Ansibleguy76 ansibleforms |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | AnsibleForms is a self-hosted web application that turns automation into self-service forms. Prior to 6.2.1, AnsibleForms uses a public hard-coded fallback JWT signing secret from server/config/auth.config.js when ACCESS_TOKEN_SECRET is unset. An unauthenticated attacker can sign a self-contained token with privileged claims because server/src/auth/auth_jwt.js verifies the signature without reloading the user from the database, and server/src/lib/middleware.js trusts the token's roles and options for authorization. A forged token can therefore be accepted as an administrator session, resulting in authentication bypass and full privileged API access. This issue is fixed in version 6.2.1. | |
| Title | AnsibleForms: Authentication bypass via hard-coded default JWT signing secret | |
| Weaknesses | CWE-1188 CWE-287 CWE-798 |
|
| References |
| |
| Metrics |
cvssV3_1
|