admin/cvelist
1
0
Fork 0
mirror of https://github.com/CVEProject/cvelist.git synced 2025-08-04 08:44:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

"-Synchronized-Data."

Browse Source
This commit is contained in:
CVE Team 2020-05-12 17:01:27 +00:00
parent a4945b2afc
commit 3c621b3b81
No known key found for this signature in database
GPG Key ID: 5708902F06FEF743
2 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
2020/12xxx/CVE-2020-12823.json Normal file
View File

@ -0,0 +1,18 @@
{
"data_type": "CVE",
"data_format": "MITRE",
"data_version": "4.0",
"CVE_data_meta": {
"ID": "CVE-2020-12823",
"ASSIGNER": "cve@mitre.org",
"STATE": "RESERVED"
},
"description": {
"description_data": [
{
"lang": "eng",
"value": "** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided."
}
]
}
}

2
2020/5xxx/CVE-2020-5248.json
View File

@ -35,7 +35,7 @@
"description_data": [
{
"lang": "eng",
"value": "GLPI before before version 9.4.6 has a vulnerability involving a default encryption key.\nGLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key.\n\nIt is possible to change the key before installing GLPI. But on existing instances, data must be reencrypted with the new key.\nProblem is we can not know which columns or rows in the database are using that; espcially from plugins. \nChanging the key without updating data would lend in bad password sent from glpi; but storing them again from the UI will work."
"value": "GLPI before before version 9.4.6 has a vulnerability involving a default encryption key. GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key. It is possible to change the key before installing GLPI. But on existing instances, data must be reencrypted with the new key. Problem is we can not know which columns or rows in the database are using that; espcially from plugins. Changing the key without updating data would lend in bad password sent from glpi; but storing them again from the UI will work."
}
]
},