PyJWT におけるアクセス制御に関する脆弱性
| Title |
PyJWT におけるアクセス制御に関する脆弱性
|
| Summary |
PyJWT には、アクセス制御に関する脆弱性が存在します。
|
| Possible impacts |
情報を改ざんされる可能性があります。 |
| Solution |
ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date |
June 22, 2017, midnight |
| Registration Date |
Sept. 28, 2017, 3:07 p.m. |
| Last Update |
Sept. 28, 2017, 3:07 p.m. |
|
CVSS3.0 : 重要
|
| Score |
7.5
|
| Vector |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
|
CVSS2.0 : 警告
|
| Score |
5
|
| Vector |
AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected System
| PyJWT project |
|
PyJWT 1.5.0 およびそれ以前
|
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
Change Log
| No |
Changed Details |
Date of change |
| 0 |
[2017年09月28日]
掲載 |
Feb. 17, 2018, 10:37 a.m. |
NVD Vulnerability Information
CVE-2017-11424
| Summary |
In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.
|
| Publication Date |
Aug. 25, 2017, 1:29 a.m. |
| Registration Date |
Jan. 26, 2021, 1:12 p.m. |
| Last Update |
Nov. 21, 2024, 12:07 p.m. |
Affected software configurations
| Configuration1 |
or higher |
or less |
more than |
less than |
| cpe:2.3:a:pyjwt_project:pyjwt:*:*:*:*:*:*:*:* |
|
1.5.0 |
|
|
| Configuration2 |
or higher |
or less |
more than |
less than |
| cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:* |
|
|
|
|
| cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:* |
|
|
|
|
Related information, measures and tools
Common Vulnerabilities List