Spot the Difference: Earth Kasha's New LODEINFO Campaign And The Correlation Analysis With The APT10 Umbrella
The encrypted payload is embedded in the legitimate digital signature by abusing MS13-098/CVE-2013-3900.
CVE-2013-3900 KEVPublic exploit Medium · 5.5 EPSS 44.6%
Microsoft WinVerifyTrust function Remote Code Execution
Microsoft · WinVerifyTrust function
Summary
The WinVerifyTrust function in Microsoft Windows mishandles Authenticode signature verification for portable executable (PE) files, so a signed executable can carry added code without the signature being invalidated. An anonymous attacker who can supply a modified signed PE file needs a local user or application to run or install it, and the attack requires user interaction; the stricter verification that addresses this is an opt-in registry setting (EnableCertPaddingCheck) that must be enabled manually.
Official description · NVD
Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update the Security Updates table and to inform customers that the EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11. While the format is different from the original CVE published in 2013, except for clarifications about how to configure the EnableCertPaddingCheck registry value, the information herein remains unchanged from the original text published on December 10, 2013, Microsoft does not plan to enforce the stricter verification behavior as a default functionality on supported releases of Microsoft Windows. This behavior remains available as an opt-in feature via reg key setting, and is available on supported editions of Windows released since December 10, 2013. This includes all currently supported versions of Windows 10 and Windows 11. The supporting code for this reg key was incorporated at the time of release for Windows 10 and Windows 11, so no security update is required; however, the reg key must be set. See the Security Updates table for the list of affected software. Vulnerability Description A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for portable executable (PE) files. An anonymous attacker could exploit the vulnerability by modifying an existing signed executable file to leverage unverified portions of the file in such a way as to add malicious code to the file without invalidating the signature. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of this vulnerability requires that a user or application run or install a specially crafted, signed PE file. An attacker could modify an... See more at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown. Breakdown
80.5 / 100
- Exploited
- Yes, in CISA KEV
- Reports
- 1
- Tactics
- 2/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.How attackers get in
What they do
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 8 months after disclosure. Public exploit code (PoC-in-GitHub) appeared 9 years after disclosure.
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+8 mo
- Added to CISA KEVEU database agrees+8 yrs
- Public exploit codePoC-in-GitHub+9 yrs
- Named in a threat reporttrendmicro.com+11 yrs
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order, 2 cited passages 2ExecutionTA0002
Malicious File T1204.002 Medium Confidence (technique links)How sure Patchfirst is that an ATT&CK technique applies to this CVE. High and medium links are shown by default; low ones come from early or generic mappings, text matching, or contradict the CVE’s details.
AI mapping from the description · how it is exploited
User runs malicious signed executable
Exploitation of this vulnerability requires that a user or application run or install a specially crafted, signed PE file
Defense Impairment
Code Signing T1553.002 Medium Confidence (technique links)How sure Patchfirst is that an ATT&CK technique applies to this CVE. High and medium links are shown by default; low ones come from early or generic mappings, text matching, or contradict the CVE’s details.
AI mapping from the description · primary impact
Tampering with signed binaries bypasses signature validation
modifying an existing signed executable file to leverage unverified portions of the file
Lower-confidence links (2)
These come from early or generic mappings, text matching, or contradict this CVE’s details (for example a public-facing technique on a bug that needs a user to open a file). Shown for completeness.
- Exploit Public-Facing ApplicationT1190 needs user interaction; not a public-facing exploit
- Steal Web Session CookieT1539 CTID attack_to_cve Phase 1 "Uncategorized" mapping (not staged by impact)
Detection
0 rules for this CVE · 40 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2013-3900 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Malicious FileT1204.00239 general rules
- Droppers Exploiting CVE-2017-11882criticalstable
- Ursnif Malware C2 URL Patterncriticalstable
- Exploit for CVE-2017-8759criticaltest
- Potential Maze Ransomware Activitycriticaltest
- File With Uncommon Extension Created By An Office Applicationhightest
- Flash Player Update from Suspicious Locationhightest
- GAC DLL Loaded Via Office Applicationshightest
- HackTool - LittleCorporal Generated Maldoc Injectionhightest
Code SigningT1553.0021 general rule
- Potential Secure Deletion with SDeletemediumtest
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Named in 1 threat report1 reportTrend MicroNov 2024
Reports are matched by finding the exact id CVE-2013-3900 in their text; nobody has reviewed the match. One passage is shown per report, at most 320 characters, linked to the original.
Also mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- Actively_Exploited_Kev | Oct 22, 202621 Oct 2026
- 44 more on OTX