summaryrefslogtreecommitdiff
path: root/python
diff options
context:
space:
mode:
authorJoseph Sutton <josephsutton@catalyst.net.nz>2022-05-30 19:16:02 +1200
committerJule Anger <janger@samba.org>2022-07-27 10:52:36 +0000
commit52dd9f8f835bc23415ec51dcc344478497e208c3 (patch)
tree4fa2e7bc59ee850c751996d920a5c8ff81a41c34 /python
parent484c6980befb86f7d81d708829ed4ceb819538eb (diff)
downloadsamba-52dd9f8f835bc23415ec51dcc344478497e208c3.tar.gz
samba-52dd9f8f835bc23415ec51dcc344478497e208c3.tar.bz2
samba-52dd9f8f835bc23415ec51dcc344478497e208c3.zip
CVE-2022-32744 s4:kpasswd: Ensure we pass the kpasswd server principal into krb5_rd_req_ctx()
To ensure that, when decrypting the kpasswd ticket, we look up the correct principal and don't trust the sname from the ticket, we should pass the principal name of the kpasswd service into krb5_rd_req_ctx(). However, gensec_krb5_update_internal() will pass in NULL unless the principal in our credentials is CRED_SPECIFIED. At present, our principal will be considered obtained as CRED_SMB_CONF (from the cli_credentials_set_conf() a few lines up), so we explicitly set the realm again, but this time as CRED_SPECIFIED. Now the value of server_in_keytab that we provide to smb_krb5_rd_req_decoded() will not be NULL. BUG: https://bugzilla.samba.org/show_bug.cgi?id=15074 Signed-off-by: Joseph Sutton <josephsutton@catalyst.net.nz> Reviewed-by: Andreas Schneider <asn@samba.org>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions