cvelist/2022/24xxx/CVE-2022-24584.json

77 lines
2.7 KiB
JSON
Raw Normal View History

2022-02-07 05:01:09 +00:00
{
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
2022-05-11 18:02:30 +00:00
"ID": "CVE-2022-24584",
"STATE": "PUBLIC"
2022-02-07 05:01:09 +00:00
},
2022-05-11 18:02:30 +00:00
"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",
2022-02-07 05:01:09 +00:00
"description": {
"description_data": [
{
"lang": "eng",
2022-05-26 00:01:36 +00:00
"value": "** DISPUTED ** Incorrect access control in Yubico OTP functionality of the YubiKey hardware tokens along with the Yubico OTP validation server. The Yubico OTP supposedly creates hardware bound second factor credentials. When a user reprograms the OTP functionality by \"writing\" it on a token using the Yubico Personalization Tool, they can then upload the new configuration to Yubicos OTP validation servers. NOTE: the vendor disputes this because there is no way for a YubiKey device to prevent a user from deciding that a secret value, which is imported into the device, should also be stored elsewhere."
2022-05-11 18:02:30 +00:00
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "n/a"
}
]
}
]
},
"references": {
"reference_data": [
{
"url": "https://upload.yubico.com/",
"refsource": "MISC",
"name": "https://upload.yubico.com/"
},
{
"url": "https://demo.yubico.com/otp/verify",
"refsource": "MISC",
"name": "https://demo.yubico.com/otp/verify"
},
{
"refsource": "MISC",
"name": "https://pastebin.com/7iLR1EbW",
"url": "https://pastebin.com/7iLR1EbW"
2022-07-01 15:00:50 +00:00
},
{
"refsource": "MISC",
"name": "https://pastebin.com/xAh8uV6J",
"url": "https://pastebin.com/xAh8uV6J"
2022-02-07 05:01:09 +00:00
}
]
}
}