dbcve.org
Profinet Inspektor NtApplication · Indu Sol

CVE-2023-49959

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-26
Fix available
A fix is available. Upgrade to 2.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In Indo-Sol PROFINET-INspektor NT through 2.4.0, a command injection vulnerability in the gedtupdater service of the firmware allows remote attackers to execute arbitrary system commands with root privileges via a crafted filename parameter in POST requests to the /api/updater/ctrl/start_update endpoint.

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 · high confidence

A command injection vulnerability exists in the gedtupdater service of Indo-Sol PROFINET-INspektor NT firmware through v2.4.0. Remote attackers can execute arbitrary system commands with root privileges by sending crafted filename parameters in POST requests to the /api/updater/ctrl/start_update endpoint. This is an unauthenticated vulnerability with critical severity due to the trivial exploitability and complete system compromise possible.

MitigationApply vendor firmware update to v2.4.1 or later. If no patch is available, isolate the device behind a firewall with strict access controls, disable the updater service if possible, and monitor for exploitation attempts.

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
Profinet Inspektor NtApplication
Affected:< 2.4.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify firmware version
    Access the device web interface or check via SSH/telnet for the firmware version. Look for a version indicator in the system status or about page, or retrieve it via an API call if available.
    Affected if The installed firmware version is lower than 2.4.1 (e.g., v2.4.0 or earlier).
  2. Confirm gedtupdater service presence
    Check if the gedtupdater service or updater component is running on the device. This may be visible in the device's service list, process list, or within the web interface under system services or running processes.
    Affected if The gedtupdater service is present and running on the device.
  3. Test vulnerable endpoint accessibility
    Attempt to access the /api/updater/ctrl/start_update endpoint via HTTP POST from an internal network host. This requires sending a POST request with a filename parameter to see if the endpoint responds.
    Affected if The endpoint responds to requests, indicating it is exposed and may accept parameters without authentication.
  4. Assess network exposure
    Review firewall rules, network configuration, or access control lists to determine if the device management interface or API endpoints are accessible from untrusted networks or the internet.
    Affected if The device or its management interface is reachable from untrusted networks without proper access controls.

A user is affected if their Indu Sol Profinet Inspektor NT firmware is below v2.4.1 AND the gedtupdater service with the vulnerable /api/updater/ctrl/start_update endpoint is accessible.

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.4.1 or later
Fixed in 2.4.1
Interim mitigation

Apply vendor firmware update to v2.4.1 or later. If no patch is available, isolate the device behind a firewall with strict access controls, disable the updater service if possible, and monitor for exploitation attempts.

Recommended fix Moderate confidence

2.4.1 or later

  1. Verify current firmware version by accessing the device web interface or checking system information
  2. Download the firmware version 2.4.1 or later from the official vendor source (indu-sol.com)
  3. Access the device administrative interface and navigate to the firmware update section
  4. Upload and apply the firmware update following the vendor's standard upgrade procedure
  5. After reboot, verify the new version is installed and the /api/updater/ctrl/start_update endpoint no longer accepts malicious input
  6. Confirm the gedtupdater service is running correctly post-update

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

Fix this in Profinet Inspektor Nt Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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