dbcve.org
Sinec InsApplication · Siemens

CVE-2024-46888

CRITICAL · 9.9 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A vulnerability has been identified in SINEC INS (All versions < V1.0 SP2 Update 3). The affected application does not properly sanitize user provided paths for SFTP-based file up- and downloads. This could allow an authenticated remote attacker to manipulate arbitrary files on the filesystem and achieve arbitrary code execution on the device.

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

Path traversal vulnerability in SINEC INS SFTP file up/download functionality. Authenticated attackers can manipulate file paths using directory traversal sequences (e.g., ../../) to write arbitrary files on the filesystem and achieve remote code execution.

MitigationUpdate to SINEC INS V1.0 SP2 Update 3 or later which includes proper path sanitization for SFTP operations.

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
Sinec InsApplication
Affected:< 1.0= 1.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 SINEC INS installation
    Check for SINEC INS installation directory (typically under C:\Program Files\Siemens\SINEC INS or /opt/siemens/sinec_ins) and locate the version information file or executable properties
    Affected if SINEC INS is installed and the version is 1.0 or lower
  2. Verify SFTP service status
    Check if the SINEC INS SFTP service is enabled and running. This is typically managed through the SINEC INS administration interface or Windows Services/systemd
    Affected if SFTP service is enabled and running on the affected version
  3. Inspect SFTP configuration
    Locate and examine SFTP-related configuration files in the SINEC INS installation directory, typically under config/sftp or similar paths. Look for any path validation settings
    Affected if SFTP configuration exists and allows unrestricted path handling (no sanitization observed)
  4. Review SFTP upload directories
    Check the file system directories configured for SFTP upload/download operations in SINEC INS. Look for writable directories accessible via SFTP
    Affected if SFTP directories are accessible without proper path traversal guards

User is affected if SINEC INS version 1.0 or lower is installed with SFTP functionality enabled, as the lack of path sanitization in SFTP operations allows directory traversal exploitation.

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

Update to SINEC INS V1.0 SP2 Update 3 or later which includes proper path sanitization for SFTP operations.

Recommended fix High confidence

V1.0 SP2 Update 3

  1. 1. Identify the current installed version of SINEC INS by accessing the system information or administration console.
  2. 2. Navigate to the Siemens Industry Online Support (SIOS) portal or official Siemens download page to obtain SINEC INS V1.0 SP2 Update 3 or later.
  3. 3. Review the release notes and upgrade instructions provided by Siemens for V1.0 SP2 Update 3.
  4. 4. Create a complete backup of the current SINEC INS configuration and any critical data.
  5. 5. Follow the official Siemens upgrade procedure to install V1.0 SP2 Update 3, ensuring all pre-requisites are met.
  6. 6. After upgrade, verify the installation was successful and the version displays as V1.0 SP2 Update 3 or later.
  7. 7. Validate that the SFTP functionality works correctly and the path traversal vulnerability is remediated.

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

Fix this in Sinec Ins Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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