"-Synchronized-Data."

This commit is contained in:
CVE Team 2020-10-04 05:01:46 +00:00
parent 7fd65345de
commit 1a91c2bd45
No known key found for this signature in database
GPG Key ID: 5708902F06FEF743

View File

@ -0,0 +1,82 @@
{
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2017-18924",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "n/a",
"version": {
"version_data": [
{
"version_value": "n/a"
}
]
}
}
]
},
"vendor_name": "n/a"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "** DISPUTED ** oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states 'As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn't describe this as a \"vulnerability\" with the library per se.'"
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "n/a"
}
]
}
]
},
"references": {
"reference_data": [
{
"url": "https://tools.ietf.org/html/rfc7636",
"refsource": "MISC",
"name": "https://tools.ietf.org/html/rfc7636"
},
{
"url": "https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15",
"refsource": "MISC",
"name": "https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15"
},
{
"url": "https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467",
"refsource": "MISC",
"name": "https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467"
},
{
"url": "https://github.com/oauthjs/node-oauth2-server/issues/637",
"refsource": "MISC",
"name": "https://github.com/oauthjs/node-oauth2-server/issues/637"
},
{
"url": "https://github.com/oauthjs/node-oauth2-server/pull/452",
"refsource": "MISC",
"name": "https://github.com/oauthjs/node-oauth2-server/pull/452"
}
]
}
}