blob: a1b15a2d586116dadec535893575990e612eb28a (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
|
References:
http://seclists.org/oss-sec/2013/q1/598
Description: information leak in crypto API
Notes:
jmm> This ID is about
jmm> For the module name we should copy only as many bytes as module_name() returns -- not as much as the destination buffer could hold. But the current code does not and therefore copies random data from behind the end of the module name, as the module name is always shorter than CRYPTO_MAX_ALG_NAME.
Bugs:
upstream: released (3.9-rc1) [9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6]
2.6.32-upstream-stable: N/A "introduced in 3.2 commit a38f7907b926"
sid: released (3.2.41-1)
2.6.32-squeeze-security: N/A "introduced in 3.2 commit a38f7907b926"
3.2-upstream-stable: released (3.2.41) [crypto-user-fix-info-leaks-in-report-api.patch]
|
