DskmsApplication · Csdeshang

CVE-2024-0413

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to after 3.1.2 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
A vulnerability was found in DeShang DSKMS up to 3.1.2. It has been rated as problematic. This issue affects some unknown processing of the file public/install.php. The manipulation leads to improper access controls. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250433 was assigned to this 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 confidence

A critical improper access control vulnerability exists in the public/install.php file of DeShang DSKMS up to version 3.1.2. The installation script is accessible remotely without authentication, potentially allowing attackers to re-run or manipulate the installation process to gain unauthorized access or control over the application.

MitigationRestrict or block remote access to install.php via web server configuration (e.g., .htaccess, nginx location blocks) or remove/delete the installation files after initial setup is complete. Implement proper authentication for any installation or configuration functions.

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
DskmsApplication
Affected:>= 3.1.0, <= 3.1.2

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 if the application is DeShang DSKMS
    Locate the application directory and check for version indicators such as a version.php file, composer.json, or application configuration files that identify the product as Csdeshang DSKMS
    Affected if The application is identified as Csdeshang DSKMS
  2. Check the installed version number
    Examine the version file, composer.json, or application configuration to determine the exact version number of the DSKMS installation
    Affected if The version is 3.1.0, 3.1.1, or 3.1.2 (falls within >= 3.1.0 and <= 3.1.2)
  3. Verify if public/install.php exists on the server
    Check the file system for the presence of the install.php file in the public or web-accessible directory of the application
    Affected if The file public/install.php exists on the server
  4. Test if install.php is remotely accessible
    Send an HTTP request to the install.php endpoint (e.g., GET /public/install.php) to verify it responds without authentication
    Affected if The install.php file is accessible over HTTP/HTTPS without requiring authentication
  5. Check if installation files have been removed or protected
    Inspect web server configuration (htaccess, nginx config) or look for indicators that access to install.php has been restricted
    Affected if No access controls or web server restrictions are in place to block access to install.php and the file remains accessible

You are affected if you are running Csdeshang DSKMS version 3.1.0 through 3.1.2 and the public/install.php file remains accessible without authentication on your web server.

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.

From vendor data
Upgrade available Upgrade to a release after 3.1.2
Interim mitigation

Restrict or block remote access to install.php via web server configuration (e.g., .htaccess, nginx location blocks) or remove/delete the installation files after initial setup is complete. Implement proper authentication for any installation or configuration functions.

Fix this in Dskms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0413 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