nocobase JWT Service jwt-service.ts hard-coded key
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.9.23, 1.9.0-beta.18, 2.0.0-alpha.52
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
A vulnerability was detected in nocobase up to 1.9.4/2.0.0-alpha.37. The affected element is an unknown function of the file nocobase\packages\core\auth\src\base\jwt-service.ts of the component JWT Service. The manipulation of the argument API_KEY results in use of hard-coded cryptographic key . The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- n/a nocobase
1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 2.0.0-alpha.0, 2.0.0-alpha.1, 2.0.0-alpha.2, 2.0.0-alpha.3, 2.0.0-alpha.4, 2.0.0-alpha.5, 2.0.0-alpha.6, 2.0.0-alpha.7, 2.0.0-alpha.8, 2.0.0-alpha.9, 2.0.0-alpha.10, 2.0.0-alpha.11, 2.0.0-alpha.12, 2.0.0-alpha.13, 2.0.0-alpha.14, 2.0.0-alpha.15, 2.0.0-alpha.16, 2.0.0-alpha.17, 2.0.0-alpha.18, 2.0.0-alpha.19, 2.0.0-alpha.20, 2.0.0-alpha.21, 2.0.0-alpha.22, 2.0.0-alpha.23, 2.0.0-alpha.24, and 13 more
- @nocobase/authnpm
From 1.9.0 · fixed in 1.9.23
- @nocobase/authnpm
fixed in 1.9.0-beta.18
- @nocobase/authnpm
From 2.0.0-alpha.1 · fixed in 2.0.0-alpha.52