Free Privileged Account Discovery Tool: Identify & secure credentials to stop lateral movement. Download Free

BeyondTrust
  • Products
    Privileged Password Management
    Discover, manage, audit, and monitor privileged accounts
    Password Safe DevOps Secrets Safe
    Endpoint Privilege Management
    Manage privileges on Windows, Mac, Linux, and Unix endpoints
    Windows and Mac Unix and Linux Active Directory Bridge
    Secure Remote Access
    Centrally manage and secure remote access for service desks and vendors
    Remote Support Privileged Remote Access
    BeyondInsight Analytics
    See All Solutions
  • Resources

    Universal Privilege Management

    Our innovative Universal Privilege Management approach secures every user, asset, and session across your entire enterprise.

    Watch Video

    Learn

    Case Studies
    Competitor Comparisons
    Datasheets
    Glossary
    Product Demos
    Whitepapers

    Attend

    Events
    Go Beyond
    Training
    Webinars

    Support

    Changelog
    Professional Services
    Technical Documentation
  • Blog
  • Partners
  • Contact
  • Support
  • Services
  • Training
  • Events
  • Company

A Quick Look at MS14-068

November 21, 2014

  • Blog
  • Archive
Microsoft recently released an out of band patch for Kerberos. Taking a look at the Microsoft security bulletin, it seems like there is some kind of issue with Kerberos signatures related to tickets. Kerebos-checksum-1 Further information is available in the Microsoft SRD Blog post: microsoft-srd-blogpost So it looks like there is an issue with PAC signatures. But what specifically? If we take a look at the kdsvc.dll patch for Server 2008, there are 3 changed functions: 3 As expected, two of the three involve PAC (Privilege Attribute Certificate). VerifyPacSignature looks promising. Let’s see what changed there. CadddptureMore or less, a comparison like above ( cmp <something>, 0xFFFFFF76 ) was added in two places. The result of this comparison will either lead to further processing or to returning a Kerberos specific error as seen below. 5 The value 0xFFFFFF76 can be traced upward in the patched function to a nearby call to _CDLocateChecksum. 6 This function is imported from cryptdll.dll, so opening that in IDA we can follow the second argument to CDLocateChecksum and see that the source of this value seems to come from the _CheckSumFns array. 7 Tracing XREFS to this array, CDRegisterCheckSum appears to be the only other place it is used and is most likely where it gets set. 8 Taking a look at CDRegisterCheckSum, it seems to take an argument and register it into the _CheckSumFns array. 666 XREFS to this function are illustrative of actual population of the array – xrefs-to-CDRegister Moving back to LoadCheckSums(), we find the source of this constant nicely formatted with Windows symbols. load-checksums Each of these arguments to CDRegisterChecksum is a structure defined like so DWORD identifier DWORD checkSumSize DWORD dunno <several function pointers> 11 If we take this data and look at the Microsoft specification for PAC [MS-PAC], we can see that it is somewhat inconsistent. Under section 2.8, we can find details about the PAC signature data: signature-type It is apparent from above, that although the spec says you are only allowed to use those three, we have quite a few more available to us as a client including CRC32. Therefore, getting back to the patch, it appears now that VerifyPacSignature is ensuring that the SignatureType is 0xFFFFFF76 (HMAC_MD5) before continuing processing.

Scott Lang

Sr. Director, Product Marketing at BeyondTrust

Scott Lang has nearly 20 years of experience in technology product marketing, currently guiding the product marketing strategy for BeyondTrust’s privileged account management solutions and vulnerability management solutions. Prior to joining BeyondTrust, Scott was director of security solution marketing at Dell, formerly Quest Software, where he was responsible for global security campaigns, product marketing for identity and access management and Windows server management.

Stay Up To Date

Get the latest news, ideas, and tactics from BeyondTrust. You may unsubscribe at any time.

I agree to receive product related communications from BeyondTrust as detailed in the Privacy Policy, and I may manage my preferences or withdraw my consent at any time.

You May Also Be Interested In:

Webcasts | February 09, 2021

Customer Webinar: Remote Support 21.1 Released!

Webcasts | February 24, 2021

Your PAM 2021 Blueprint: Securing Privileged Accounts for On-Premises and Cloud Assets

Whitepapers

Evolving Privileged Identity Management (PIM) In The 'Next Normal'

BeyondTrust Logo
  • Facebook
  • Twitter
  • LinkedIn

Keep up with BeyondTrust

I agree to receive product related communications from BeyondTrust as detailed in the Privacy Policy, and I may manage my preferences or withdraw my consent at any time.

Customer Support
Contact Sales

Products

  • Endpoint Privilege Management
  • Password Management
  • Privileged Remote Access
  • DevOps Secrets Safe
  • Remote Support

Resources

  • Blog
  • Case Studies
  • Competitor Comparisons
  • Datasheets
  • Glossary
  • Videos
  • Webcasts
  • Whitepapers

About

  • Company
  • Careers
  • Contact
  • Events
  • Leadership Team
  • Partner Program
  • Press

Languages

  • English
  • German
  • French
  • Spanish
  • Korean
  • Portuguese
  • Japanese
  • Privacy
  • Security
  • Manage Cookies
  • WEEE Compliance

Copyright © 1999 — 2020 BeyondTrust Corporation. All rights reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust Corporation is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.