CVE-2024-46894
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 · uneditedA vulnerability has been identified in SINEC INS (All versions < V1.0 SP2 Update 3). The affected application does not properly validate authorization of a user to query the "/api/sftp/users" endpoint. This could allow an authenticated remote attacker to gain knowledge about the list of configured users of the SFTP service and also modify that configuration.
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 · moderate confidenceThis is a broken access control (IDOR) vulnerability in SINEC INS where the /api/sftp/users endpoint lacks proper authorization validation. An authenticated attacker can enumerate SFTP service users and modify the configuration without proper permission checks.
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<= 1.0= 1.0CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify SINEC INS installation versionLocate the SINEC INS installation directory or check the product version through the Siemens software management interface. Common paths include the program files directory where Siemens software is installed, or check the version displayed in the SINEC INS web interface under System > About or similar system information section.Affected if The installed version is SINEC INS version 1.0 or any version below 1.0 SP2 Update 3
-
Verify SFTP service is configuredAccess the SINEC INS administrative interface and navigate to the SFTP service configuration area. Look for SFTP user management settings, typically found under Services > SFTP or Network > SFTP Configuration in the web interface.Affected if SFTP service is enabled and users are configured in SINEC INS
-
Confirm API endpoint accessibilityAttempt to access the /api/sftp/users endpoint via HTTP/HTTPS request using a web browser or API tool (such as curl). This endpoint should be reachable if the SINEC INS web server is running.Affected if The /api/sftp/users endpoint returns a response (either success or error) rather than a 404 or access denied message
-
Test authorization on the endpointUsing an authenticated user account with standard or limited permissions, make a request to /api/sftp/users. Observe whether the response returns user list data or allows modification operations without proper authorization checks.Affected if The endpoint returns SFTP user information or allows configuration changes without verifying the requester has administrative privileges
You are affected if running SINEC INS version 1.0 or lower AND the SFTP service is enabled, since the vulnerable /api/sftp/users endpoint lacks authorization checks in these versions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to SINEC INS V1.0 SP2 Update 3 or later which implements proper authorization validation on the /api/sftp/users endpoint.
V1.0 SP2 Update 3
- Identify the current version of SINEC INS installed in the environment
- Review the SINEC INS release notes and compatibility documentation for V1.0 SP2 Update 3
- Plan the upgrade considering any dependencies and system requirements
- Back up the current SINEC INS configuration and data
- Upgrade SINEC INS to version V1.0 SP2 Update 3 or later
- After upgrade, verify that the /api/sftp/users endpoint now properly validates authorization
- Confirm that only authorized users can query or modify SFTP user configurations
- Test that the application functions normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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