CVE-2024-6098
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 · uneditedWhen performing an online tag generation to devices which communicate using the ControlLogix protocol, a machine-in-the-middle, or a device that is not configured correctly, could deliver a response leading to unrestricted or unregulated resource allocation. This could cause a denial-of-service condition and crash the Kepware application. By default, these functions are turned off, yet they remain accessible for users who recognize and require their advantages.
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 confidenceIn Kepware's OPC server software, the online tag generation feature for ControlLogix devices lacks proper validation and resource limits when processing device responses. A malicious or misconfigured device performing a machine-in-the-middle attack can send specially crafted responses that cause unrestricted memory or CPU allocation, leading to application crash and denial of service.
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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Kepware OPC Server installation and versionCheck the Windows registry under HKLM\SOFTWARE\Kepware or inspect the installation directory (typically C:\Program Files\Kepware) for the version information file or check Programs and Features in Control PanelAffected if Kepware OPC Server version is installed and matches the affected version range (the online tag generation feature exists in the software)
-
Verify online tag generation feature status for ControlLogixOpen Kepware Configuration (KEPServerEX) and navigate to the ControlLogix device driver properties. Locate the 'Online Tag Generation' or 'Tag Update' settings. Alternatively, check the project's XML configuration file for <TagUpdate> or <OnlineTagGeneration> settings within the ControlLogix driver sectionAffected if Online tag generation is explicitly enabled (it is disabled by default per the summary)
-
Inspect device communication logs for abnormal responsesReview Kepware's diagnostic logs or event logs for unusually large device responses, memory allocation warnings, or CPU spikes tied to ControlLogix device pollingAffected if Logs show excessive memory allocation or CPU consumption triggered by ControlLogix device responses, or the application has crashed recently with memory-related errors
-
Assess network isolation of the Kepware serverCheck network configuration to determine if the Kepware server is on a dedicated network segment with only trusted ControlLogix devices, or if it is accessible from untrusted networksAffected if The server is on a shared or untrusted network segment where an unauthorized or malicious device could perform MITM attacks against the ControlLogix communication
A user is affected if they have Kepware OPC Server installed with online tag generation enabled for ControlLogix devices AND the server is accessible to untrusted or potentially malicious devices on the network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataKeep the online tag generation functions disabled (default state) unless strictly required. When enabled, ensure Kepware server is isolated on a dedicated network segment with only trusted ControlLogix devices. Consider network access control lists to prevent unauthorized devices from communicating with the server.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6098 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6098 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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