aboutsummaryrefslogtreecommitdiff
path: root/src/lib/kadm5/kadm_rpc.h
diff options
context:
space:
mode:
authorGreg Hudson <ghudson@mit.edu>2015-11-01 22:45:21 -0500
committerTom Yu <tlyu@mit.edu>2015-11-25 17:00:42 -0500
commit9ffff96c98a93bd9bc3846ac044a34cb1566aae7 (patch)
tree3a8a40a5b58814415ae452487303ceaa4b54c39d /src/lib/kadm5/kadm_rpc.h
parent491d7d5182458fcf4025aa43a89462119d8df7f1 (diff)
downloadkrb5-9ffff96c98a93bd9bc3846ac044a34cb1566aae7.zip
krb5-9ffff96c98a93bd9bc3846ac044a34cb1566aae7.tar.gz
krb5-9ffff96c98a93bd9bc3846ac044a34cb1566aae7.tar.bz2
Fix IAKERB context export/import [CVE-2015-2698]
The patches for CVE-2015-2696 contained a regression in the newly added IAKERB iakerb_gss_export_sec_context() function, which could cause it to corrupt memory. Fix the regression by properly dereferencing the context_handle pointer before casting it. Also, the patches did not implement an IAKERB gss_import_sec_context() function, under the erroneous belief that an exported IAKERB context would be tagged as a krb5 context. Implement it now to allow IAKERB contexts to be successfully exported and imported after establishment. CVE-2015-2698: In any MIT krb5 release with the patches for CVE-2015-2696 applied, an application which calls gss_export_sec_context() may experience memory corruption if the context was established using the IAKERB mechanism. Historically, some vulnerabilities of this nature can be translated into remote code execution, though the necessary exploits must be tailored to the individual application and are usually quite complicated. CVSSv2 Vector: AV:N/AC:H/Au:S/C:C/I:C/A:C/E:POC/RL:OF/RC:C (cherry picked from commit 3db8dfec1ef50ddd78d6ba9503185995876a39fd) (cherry picked from commit 54222de30a89bfac0247dfbc1759556dc9fd2983) ticket: 8284 (new) version_fixed: 1.13.3
Diffstat (limited to 'src/lib/kadm5/kadm_rpc.h')
0 files changed, 0 insertions, 0 deletions