CVE-2024-0400
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 · uneditedSCM Software is a client and server application. An Authenticated System manager client can execute LINQ query in the SCM server, for customized filtering. An Authenticated malicious client can send a specially crafted code to skip the validation and execute arbitrary code (RCE) on the SCM Server remotely. Malicious clients can execute any command by using this RCE vulnerability.
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 an authenticated remote code execution vulnerability in SCM Software where an authenticated System manager client can bypass validation in the LINQ query filtering functionality to inject and execute arbitrary code on the SCM Server remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SCM Software installation and versionLocate the SCM Software installation directory and check the version information (typically in a version file, about dialog, or executable properties). Compare your installed version against any officially documented affected versions for CVE-2024-0400.Affected if The installed SCM Software version falls within an affected version range and the System manager client feature is accessible.
-
Verify System manager client access is enabledCheck the SCM Server configuration settings or user role definitions to determine whether the System manager client functionality is enabled and accessible to any authenticated users.Affected if System manager client access is enabled and users with this role can connect to the SCM Server.
-
Inspect LINQ query filtering configurationReview the SCM Server configuration files or settings related to LINQ query filtering to determine if the filtering functionality that lacks proper input validation is exposed and operational.Affected if The LINQ query filtering functionality is enabled and accessible to authenticated System manager clients.
-
Check authentication enforcement on System manager interfaceExamine the authentication and authorization configuration for the System manager client interface to verify whether proper validation is enforced on incoming requests.Affected if The System manager interface relies on the vulnerable LINQ query filtering without sufficient input validation.
A user is affected if they run an SCM Software version within the affected range with the System manager client feature enabled and the vulnerable LINQ query filtering functionality exposed to authenticated users.
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.
From vendor dataImplement strict input validation and parameterized queries for LINQ operations, enforce proper authentication and authorization checks on all client requests, and apply network segmentation to limit System manager client access.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0400 — 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-0400 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