dbcve.org
SequencemanagerApplication · Rockwellautomation

CVE-2024-6436

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-27
Fix available
A fix is available. Upgrade to 2.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An input validation vulnerability exists in the Rockwell Automation Sequence Manager™ which could allow a malicious user to send malformed packets to the server and cause a denial-of-service condition. If exploited, the device would become unresponsive, and a manual restart will be required for recovery. Additionally, if exploited, there could be a loss of view for the downstream equipment sequences in the controller. Users would not be able to view the status or command the equipment sequences, however the equipment sequence would continue to execute uninterrupted.

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

An input validation vulnerability in Rockwell Automation Sequence Manager allows malformed packets to cause denial-of-service. Exploitation renders the device unresponsive, requiring manual restart, and results in loss of view for downstream equipment sequences while the equipment continues executing.

MitigationImplement proper input validation and bounds checking on incoming packets to prevent malformed data from causing DoS conditions. Apply vendor patches when available.

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
SequencemanagerApplication
Affected:< 2.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm Rockwell Automation Sequence Manager is installed
    Identify if the Sequence Manager software is present on the system or network device by reviewing installed software, running processes, or device firmware information
    Affected if Sequence Manager is present on the system
  2. Determine the installed version of Sequence Manager
    Use system inventory tools, software listing commands, or check the product's about/version information panel to obtain the exact version number
    Affected if The version cannot be determined or is lower than 2.0
  3. Compare installed version against affected range
    Document the version number and compare it to the affected range of versions less than 2.0
    Affected if The installed version is 1.x or any version below 2.0
  4. Assess network exposure to Sequence Manager
    Review network configuration to determine if Sequence Manager accepts incoming network packets from untrusted sources
    Affected if The product is network-accessible and can receive packets from external or less-trusted systems

A system is affected if Rockwell Automation Sequence Manager is installed and the version is below 2.0, making it vulnerable to malformed packet input validation issues.

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 2.0 or later
Fixed in 2.0
Interim mitigation

Implement proper input validation and bounds checking on incoming packets to prevent malformed data from causing DoS conditions. Apply vendor patches when available.

Recommended fix Moderate confidence

Sequence Manager 2.0 or later

  1. 1. Identify the current installed version of Rockwell Automation Sequence Manager by accessing the product interface or checking system documentation.
  2. 2. Navigate to the official Rockwell Automation support website or partner download portal.
  3. 3. Locate and download Sequence Manager version 2.0 or later.
  4. 4. Before applying the upgrade, review release notes for any prerequisites or migration requirements.
  5. 5. Apply the upgrade following the vendor's standard installation procedure.
  6. 6. After upgrade, verify the Sequence Manager is operational and monitor for normal function.
  7. 7. Test that downstream equipment sequences are visible and controllable from the controller interface.
Caveat Review release notes for any configuration or compatibility changes before upgrading

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

Fix this in Sequencemanager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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