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-09-01 20:01:41 +00:00
parent 2129aa4aac
commit 03a21e241a
No known key found for this signature in database
GPG Key ID: 5708902F06FEF743
3 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
2019/17xxx/CVE-2019-17638.json
View File

@ -34,7 +34,7 @@
"description_data": [
{
"lang": "eng",
"value": "In Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double release, two threads can acquire the same ByteBuffer from the pool and while thread1 is about to use the ByteBuffer to write response1 data, thread2 fills the ByteBuffer with other data. Thread1 then proceeds to write the buffer that now contains different data. This results in client1, which issued request1 seeing data from another request or response which could contain sensitive data belonging to client2 (HTTP session ids, authentication credentials, etc.). If the Jetty version cannot be upgraded, the vulnerability can be significantly reduced by configuring a responseHeaderSize significantly larger than the requestHeaderSize (12KB responseHeaderSize and 8KB requestHeaderSize)."
"value": "In Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double release, two threads can acquire the same ByteBuffer from the pool and while thread1 is about to use the ByteBuffer to write response1 data, thread2 fills the ByteBuffer with other data. Thread1 then proceeds to write the buffer that now contains different data. This results in client1, which issued request1 seeing data from another request or response which could contain sensitive data belonging to client2 (HTTP session ids, authentication credentials, etc.). If the Jetty version cannot be upgraded, the vulnerability can be significantly reduced by configuring a responseHeaderSize significantly larger than the requestHeaderSize (12KB responseHeaderSize and 8KB requestHeaderSize)."
}
]
},
@ -77,4 +77,4 @@
}
]
}
}
}

5
2020/13xxx/CVE-2020-13933.json
View File

@ -53,6 +53,11 @@
"refsource": "MLIST",
"name": "[geode-dev] 20200831 Proposal to bring GEODE-8456 (shiro upgrade) to support branches",
"url": "https://lists.apache.org/thread.html/r18b45d560d76c4260813c802771cc9678aa651fb8340e09366bfa198@%3Cdev.geode.apache.org%3E"
},
{
"refsource": "MLIST",
"name": "[geode-dev] 20200901 Re: Proposal to bring GEODE-8456 (shiro upgrade) to support branches",
"url": "https://lists.apache.org/thread.html/r9ea6d8560d6354d41433ad006069904f0ed083527aa348b5999261a7@%3Cdev.geode.apache.org%3E"
}
]
},

5
2020/24xxx/CVE-2020-24034.json
View File

@ -66,6 +66,11 @@
"refsource": "FULLDISC",
"name": "20200901 Sagemcom router insecure deserialization > privilege escalation",
"url": "http://seclists.org/fulldisclosure/2020/Sep/3"
},
{
"refsource": "MISC",
"name": "http://packetstormsecurity.com/files/159026/Sagemcom-F-ST-5280-Privilege-Escalation.html",
"url": "http://packetstormsecurity.com/files/159026/Sagemcom-F-ST-5280-Privilege-Escalation.html"
}
]
}