dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-1244

CRITICAL · 9.5 CVSS v4.0 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in the OSSEC HIDS agent for Windows prior to version 3.8.0 allows an attacker in with control over the OSSEC server or in possession of the agent's key to configure the agent to connect to a malicious UNC path. This results in the leakage of the machine account NetNTLMv2 hash, which can be relayed for remote code execution or used to escalate privileges to SYSTEM via AD CS certificate forging and other similar attacks.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper input validation in OSSEC HIDS Windows agent prior to 3.8.0 allows an authenticated attacker with control over the OSSEC server or possession of the agent key to configure the agent to connect to a malicious UNC path, causing the machine account NetNTLMv2 hash to be leaked for relay attacks or AD CS privilege escalation.

MitigationUpgrade OSSEC HIDS Windows agents to version 3.8.0 or later which implements proper input validation for UNC paths. If immediate upgrade is not possible, restrict access to the OSSEC server and agent keys to trusted personnel only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify OSSEC HIDS Windows agent is installed
    Check for the OSSEC service via 'sc query ossec' or look for installation directory at C:\Program Files (x86)\ossec-agent or C:\Program Files\ossec-agent
    Affected if The OSSEC Windows agent service or installation directory exists on the system
  2. Determine the installed OSSEC agent version
    Run 'ossec-agent -v' or check the version file in the installation directory (e.g., VERSION or win32ui.rc)
    Affected if The version returned is lower than 3.8.0 or the version cannot be determined (implies pre-3.8.0)
  3. Inspect the OSSEC agent configuration file
    Open the agent configuration file (typically ossec.conf in the installation directory) and locate the <server> or <client> section
    Affected if The configuration file exists and contains <server> element with an IP address or hostname that the agent connects to
  4. Check for active agent connection
    Verify the ossec service is running via 'sc query ossec' or in Services.msc
    Affected if The OSSEC agent service is running and actively attempting to connect to a server
  5. Review recent agent configuration changes
    Check Windows Event Logs under Application and Services > OSSEC for any configuration modification events or connection attempts
    Affected if The agent logs show configuration reload events or connection activity to any server

The environment is affected if OSSEC HIDS Windows agent version 3.8.0 or later is not installed, regardless of whether the agent is currently active or configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OSSEC HIDS Windows agents to version 3.8.0 or later which implements proper input validation for UNC paths. If immediate upgrade is not possible, restrict access to the OSSEC server and agent keys to trusted personnel only.

Recommended fix High confidence

OSSEC HIDS agent for Windows version 3.8.0

  1. Obtain OSSEC HIDS agent for Windows version 3.8.0 or later from the official OSSEC repository (https://github.com/ossec/ossec-hids)
  2. Backup the existing OSSEC agent configuration files (ossec.conf and any local rules)
  3. Uninstall the current OSSEC agent version if running
  4. Install the OSSEC HIDS agent version 3.8.0 for Windows
  5. Restore the backed-up configuration files
  6. Restart the OSSEC agent service to apply the update
  7. Verify the agent is running and communicating with the OSSEC server

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1244 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data