Jwt Simple Node Module
Approved changes feed: RSS · Atom
cpe:2.3:a:hackerone:jwt-simple_node_module:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Hackerone (9b72fff1-532f-502a-8030-14fc4a21dd17) |
|---|---|
| Product | Jwt Simple Node Module (cac24b8d-3799-53d8-9fba-2fb7cb5f46de) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2016-10555 |
vulnerable | 2026-06-08 05:07:25.312191 |
Details available
Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants.
Published: 2018-05-31T20:00:00.000Z
Updated: 2024-09-16T16:38:09.923Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.