LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33485: CODESYS Control Runtime system before 3.5.17.10 has a Heap-based Buffer Overflow.

CODESYS Control Runtime system before 3.5.17.10 has a Heap-based Buffer Overflow.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-33485 is a heap-based buffer overflow in CODESYS Control Runtime systems before 3.5.17.10. This matters because CODESYS runtimes are used in automation environments, but the supplied sources do not provide severity, exploitability, or affected device inventory details.

Executive priority

Treat this as a targeted OT asset-management issue until vendor-specific exposure is confirmed. Prioritize identifying affected runtimes, because business urgency depends on where the runtime is deployed and whether affected systems support safe updating.

Technical view

The CVE record states that CODESYS Control Runtime before 3.5.17.10 contains a heap-based buffer overflow. The bundle does not include CVSS, CWE, CPEs, attack vector, privileges, user interaction, or detailed vendor remediation text, so technical impact cannot be precisely scored from these sources alone.

Likely exposure

Exposure is likely limited to environments running CODESYS Control Runtime versions earlier than 3.5.17.10. The source bundle does not identify specific OEM devices, CPEs, deployment roles, or internet-facing indicators.

Exploitation context

The record is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The provided evidence does not include proof-of-concept availability, exploit maturity, or exploitation prerequisites.

Researcher notes

Source evidence is sparse: no CVSS, CWE, CPEs, affected OEM products, attack vector, or remediation detail beyond the version boundary. Do not assume exploitability or device impact without the CODESYS advisory and product-specific OEM confirmation.

Mitigation direction

  • Inventory systems running CODESYS Control Runtime.
  • Identify runtime versions and flag anything before 3.5.17.10.
  • Check CODESYS and device OEM guidance before updating.
  • Plan upgrade to 3.5.17.10 or later where supported.
  • Restrict management access to affected OT systems.
  • Monitor vendor advisories for additional remediation details.

Validation and detection

  • Confirm whether CODESYS Control Runtime is present.
  • Record exact runtime versions for each asset.
  • Compare versions against the before-3.5.17.10 affected range.
  • Review vendor advisory applicability for each device.
  • Verify compensating network controls around affected systems.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-33485 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.