dbcve.org
Qradar WincollectApplication · Ibm

CVE-2024-51461

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-11
Fix available
A fix is available. Upgrade to 10.1.14 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
IBM QRadar WinCollect Agent 10.0 through 10.1.13 could allow a remote attacker to cause a denial of service by interrupting an HTTP request that could consume memory resources.

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 · moderate confidence

IBM QRadar WinCollect Agent versions 10.0 through 10.1.13 contains a denial of service vulnerability where a remote attacker can interrupt HTTP requests to cause excessive memory consumption, potentially rendering the agent unresponsive.

MitigationUpgrade IBM QRadar WinCollect Agent to a version beyond 10.1.13 (or the latest available fixed version) to remediate this vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qradar WincollectApplication
Affected:>= 10.0, < 10.1.14

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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 IBM QRadar WinCollect Agent is installed
    Check Windows Services or the Programs and Features list for WinCollect Agent. Alternatively, search for WinCollect installation directories on the system.
    Affected if WinCollect Agent is not present on the system, this CVE does not apply.
  2. Determine the installed WinCollect Agent version
    Right-click the WinCollect Agent service in Windows Services and select Properties, or check the version information in the WinCollect installation directory. The version is typically displayed as Major.Minor.Patch (e.g., 10.1.13).
    Affected if The version cannot be determined or the agent is not installed.
  3. Compare installed version against affected range
    Compare the identified version number to the affected range: 10.0 through 10.1.13. Any version equal to or greater than 10.0 but less than 10.1.14 is vulnerable.
    Affected if The installed version is 10.0 through 10.1.13 inclusive, meaning the system is within the affected version range.
  4. Confirm HTTP-based communication is enabled
    Inspect the WinCollect Agent configuration files or the agent settings to determine if HTTP transport is configured for communicating with the QRadar console. Check the agent configuration for HTTP endpoint settings.
    Affected if HTTP communication is enabled and the version is within the affected range, the vulnerability is exploitable in this environment.

A system is affected by this CVE if IBM QRadar WinCollect Agent version 10.0 through 10.1.13 is installed and HTTP-based communication is 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
Upgrade available Upgrade to 10.1.14 or later
Fixed in 10.1.14
Interim mitigation

Upgrade IBM QRadar WinCollect Agent to a version beyond 10.1.13 (or the latest available fixed version) to remediate this vulnerability.

Recommended fix Moderate confidence

10.1.14

  1. Obtain IBM QRadar WinCollect Agent version 10.1.14 or later from IBM's official support portal or Fix Central
  2. Review IBM's upgrade documentation for WinCollect Agent before proceeding
  3. Back up current WinCollect configuration following IBM backup procedures
  4. Upgrade the WinCollect Agent to the fixed version using IBM's recommended upgrade process
  5. Verify the upgrade was successful and the service is running properly

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

Fix this in Qradar Wincollect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51461 — 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-51461 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