dbcve.org
6gk1411 1ac00 FirmwareOperating system · Siemens

CVE-2023-29107

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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
A vulnerability has been identified in SIMATIC Cloud Connect 7 CC712 (All versions >= V2.0 < V2.1), SIMATIC Cloud Connect 7 CC716 (All versions >= V2.0 < V2.1). The export endpoint discloses some undocumented files. This could allow an unauthenticated remote attacker to gain access to additional information 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

A detailed technical summary for this CVE is being prepared.

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
6gk1411 1ac00 FirmwareOperating system
Affected:= 2.0
6gk1411 5ac00 FirmwareOperating system
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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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
Patch available Apply the vendor patch
Vendor patch cert-portal.siemens.com →
Recommended fix High confidence

V2.1

  1. Verify current firmware version on the affected device (6gk1411 1ac00 or 6gk1411 5ac00) via the device web interface or management console
  2. Download the V2.1 firmware update from the Siemens Industry Online Support portal or via the vendor patch reference
  3. Review the firmware upgrade instructions in the Siemens documentation (ssa-555292.pdf) for any specific prerequisites
  4. Back up current device configuration before performing the firmware update
  5. Connect the device to a stable power source to prevent interruption during the update process
  6. Upload and install the V2.1 firmware using the device's firmware update function (typically via web-based management or TIA Portal)
  7. Verify the firmware installation was successful by checking the firmware version displays as V2.1
  8. Confirm the vulnerability is resolved by verifying the undocumented export endpoint is no longer accessible
Caveat Review Siemens release notes for V2.1 to check for any configuration or compatibility changes before upgrading

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

We can apply and verify the patch for your build — typical engagement from $1,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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