LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34599: Improper Certificate Validation in CODESYS Git

Affected versions of CODESYS Git in Versions prior to V1.1.0.0 lack certificate validation in HTTPS handshakes. CODESYS Git does not implement certificate validation by default, so it does not verify that the server provides a valid and trusted HTTPS certificate. Since the certificate of the server to which the connection is made is not properly verified, the server connection is vulnerable to a man-in-the-middle attack.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CODESYS Git versions before V1.1.0.0 did not validate HTTPS certificates by default. An attacker positioned between the user and the server could impersonate the server, exposing or changing Git traffic. The main business concern is loss of source-code confidentiality and integrity in affected engineering workflows.

Executive priority

Treat this as a high-priority engineering security fix, not a confirmed active-crisis event. Remediation protects source-code confidentiality and integrity, which may affect industrial automation development and operational trust.

Technical view

This is CWE-295 improper certificate validation in CODESYS Git HTTPS handshakes. The client does not verify that the server certificate is valid and trusted by default, leaving connections susceptible to man-in-the-middle interception or modification. CVSS 3.1 score is 7.4 high, with high confidentiality and integrity impact and no availability impact.

Likely exposure

Exposure is limited to environments using CODESYS Git versions prior to V1.1.0.0, especially when HTTPS Git operations traverse untrusted or shared networks. The bundle does not identify other affected CODESYS products.

Exploitation context

The provided sources describe a man-in-the-middle risk but do not cite public exploitation. CISA KEV status is false in the bundle, so active exploitation should not be assumed from this evidence.

Researcher notes

The evidence supports improper HTTPS certificate validation in CODESYS Git before V1.1.0.0. The advisory does not provide exploit details in the bundle, and no KEV listing is present. Avoid broad product assumptions beyond CODESYS Git.

Mitigation direction

  • Inventory installations of CODESYS Git and record exact versions.
  • Upgrade CODESYS Git to V1.1.0.0 or later where available.
  • Review the CODESYS advisory for vendor-specific remediation guidance.
  • Restrict affected Git traffic to trusted network paths until remediated.
  • Prioritize repositories containing sensitive engineering or operational source code.

Validation and detection

  • Confirm whether CODESYS Git is installed in engineering workstations or build environments.
  • Verify installed CODESYS Git versions are V1.1.0.0 or later.
  • Review configuration and vendor guidance for HTTPS certificate validation behavior.
  • Identify HTTPS Git workflows that could cross untrusted network segments.
  • Document compensating controls where upgrades are delayed.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-295: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-34599 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
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

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

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2021-34599Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CODESYSCODESYS GitCODESYS GitListed
Weakness

CWE details

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

CWE-295 · source CWE mapping

Improper Certificate Validation

Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.