| Title | jwt-simple における暗号に関する脆弱性 |
|---|---|
| Summary | jwt-simple には、暗号に関する脆弱性が存在します。 |
| Possible impacts | 情報を改ざんされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | Oct. 31, 2016, midnight |
| Registration Date | Aug. 8, 2018, 3:34 p.m. |
| Last Update | Aug. 8, 2018, 3:34 p.m. |
| CVSS3.0 : 警告 | |
| Score | 6.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CVSS2.0 : 警告 | |
| Score | 4 |
|---|---|
| Vector | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| jwt-simple project |
| jwt-simple 0.3.0 およびそれ以前 |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2018年08月08日] 掲載 |
Aug. 8, 2018, 3:34 p.m. |
| Summary | 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. |
|---|---|
| Publication Date | June 1, 2018, 5:29 a.m. |
| Registration Date | Jan. 26, 2021, 2:05 p.m. |
| Last Update | Nov. 21, 2024, 11:44 a.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:jwt-simple_project:jwt-simple:*:*:*:*:*:node.js:*:* | 0.3.0 | ||||