<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bugfix on The Manticore Project</title><link>https://themanticoreproject.com/tags/bugfix/</link><description>Recent content in Bugfix on The Manticore Project</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 17 Jun 2026 20:23:02 +0000</lastBuildDate><atom:link href="https://themanticoreproject.com/tags/bugfix/index.xml" rel="self" type="application/rss+xml"/><item><title>Manticore v1.1.5: Bug fixes</title><link>https://themanticoreproject.com/blog/manticore-v1-1-5-bug-fixes/</link><pubDate>Wed, 17 Jun 2026 20:23:02 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-1-5-bug-fixes/</guid><description>&lt;p>Manticore is a Go library of offensive and defensive security primitives maintained by The Manticore Project. This release, v1.1.5, is a maintenance update with no new features: it is a round of bug fixes focused on the LDAP and SMB clients, following the RPC work that landed in v1.1.4. The fixes fall into a few categories.&lt;/p>
&lt;h2 id="pass-the-hash-correctness-on-ldap-and-smb">Pass-the-hash correctness on LDAP and SMB&lt;/h2>
&lt;p>Two of the fixes correct pass-the-hash, on both the LDAP and the SMB stacks. LDAP pass-the-hash now performs an NTLM hash bind rather than treating the hash as a password (#657), and SMB NTLM authentication now uses the NT hash for the pass-the-hash path (#679). In both cases the supplied hash was not being fed into the right step of the NTLM exchange, so authentication from a harvested hash failed where it should have succeeded. If you authenticate with NT hashes against either protocol, this is the release you want.&lt;/p></description></item><item><title>Manticore v1.1.3: Fix ms_rrp enumeration</title><link>https://themanticoreproject.com/blog/manticore-v1-1-3-fix-ms-rrp-enumeration/</link><pubDate>Tue, 16 Jun 2026 08:59:36 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-1-3-fix-ms-rrp-enumeration/</guid><description>&lt;p>Manticore is a Go library of offensive and defensive security primitives maintained by The Manticore Project. This release, v1.1.3, is a small patch that continues the Remote Registry line of work from v1.1.1 and v1.1.2. It carries a single, focused fix: the MS-RRP enumeration corrections are restored after being lost from main.&lt;/p>
&lt;h2 id="restoring-the-ms_rrp-enumeration-fixes">Restoring the ms_rrp enumeration fixes&lt;/h2>
&lt;p>During the merges that followed the v1.1.1 Windows REG file parser and the v1.1.2 NDR marshaling fix, a pair of corrections to the MS-RRP (&lt;code>ms_rrp&lt;/code>) enumeration path were inadvertently dropped from the &lt;code>main&lt;/code> branch. This release restores them (#612, #614) in a single change (&lt;a href="https://github.com/TheManticoreProject/Manticore/pull/620">Restore ms_rrp enumeration fixes lost from main&lt;/a>).&lt;/p></description></item><item><title>Manticore v1.1.2: Registry-related fixes</title><link>https://themanticoreproject.com/blog/manticore-v1-1-2-registry-related-fixes/</link><pubDate>Tue, 16 Jun 2026 07:27:22 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-1-2-registry-related-fixes/</guid><description>&lt;p>Manticore is a Go library of offensive and defensive security primitives maintained by The Manticore Project. This release, v1.1.2, is a small patch that continues the Remote Registry and registry work started in v1.1.1. It contains a single, focused fix to how &lt;code>RPC_SECURITY_DESCRIPTOR&lt;/code> is marshaled over NDR.&lt;/p>
&lt;h2 id="rpc_security_descriptor-marshaling">RPC_SECURITY_DESCRIPTOR marshaling&lt;/h2>
&lt;p>The fix corrects &lt;code>RPC_SECURITY_DESCRIPTOR&lt;/code> marshaling when its &lt;code>size_is&lt;/code> and &lt;code>length_is&lt;/code> bounds are independent (#618). In NDR, a security descriptor is carried as a conformant-varying array of bytes: the buffer&amp;rsquo;s allocated capacity is described by &lt;code>size_is&lt;/code> (the conformance count) and the number of bytes actually present is described by &lt;code>length_is&lt;/code> (the variance count). These two values are not always equal, since a caller can allocate a larger buffer than it fills.&lt;/p></description></item><item><title>Manticore v1.0.4: Minor bug fixes on Windows KeyCredential time functions</title><link>https://themanticoreproject.com/blog/manticore-v1-0-4-keycredential-time-fixes/</link><pubDate>Wed, 29 Oct 2025 10:58:34 +0000</pubDate><guid>https://themanticoreproject.com/blog/manticore-v1-0-4-keycredential-time-fixes/</guid><description>&lt;p>Manticore is the Go library of offensive and defensive security primitives that underpins the tools of The Manticore Project. This release, &lt;strong>v1.0.4&lt;/strong>, is a small maintenance update: there are no new features, just a focused round of bug fixes in the Windows KeyCredential time handling.&lt;/p>
&lt;h2 id="keycredential-time-functions">KeyCredential time functions&lt;/h2>
&lt;p>KeyCredential blobs (the &lt;code>msDS-KeyCredentialLink&lt;/code> attribute used by Windows Hello for Business and shadow-credentials tooling) carry timestamps such as the key creation and last-update times. Getting these conversions right matters, since an off-by-one or misencoded timestamp can produce a blob that the directory rejects, or one that misrepresents when a key was created.&lt;/p></description></item></channel></rss>