dbcve.org
NoderpApplication · Shanxi Tianneng Technology

CVE-2024-1005

HIGH · 7.5 CVSS v3.1 Published 2024-01-29
Fix available
A fix is available. Upgrade to 6.0.2 or later.
See remediation →
84/100
Remediation priority · High
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 has been found in Shanxi Diankeyun Technology NODERP up to 6.0.2 and classified as critical. This vulnerability affects unknown code of the file /runtime/log. The manipulation leads to files or directories accessible. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-252274 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 directory listing vulnerability in Shanxi Diankeyun Technology NODERP up to v6.0.2 allows remote attackers to access and enumerate files in the /runtime/log directory without authentication. This exposes log contents that may contain sensitive information such as credentials, session tokens, or system details.

MitigationDisable directory listing/indexing on the web server for the /runtime/log path, or implement proper authentication and access controls. Consider restricting network access to the application if no patch is available.

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
NoderpApplication
Affected:< 6.0.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm NODERP installation
    Identify if Shanxi Diankeyun Technology NODERP or Shanxi Tianneng Technology Noderp is deployed on the system by reviewing installed applications, web server document roots, or running processes
    Affected if The product is installed and accessible over the network
  2. Check installed version
    Locate and read the version file, configuration, or application metadata to determine the running version of NODERP, then compare it against the affected range of versions prior to 6.0.2
    Affected if The installed version is lower than 6.0.2 (e.g., 6.0.1, 6.0.0, or earlier releases)
  3. Verify /runtime/log directory exists
    Check if the /runtime/log directory exists in the application web root or document directory
    Affected if The /runtime/log directory is present on the server filesystem
  4. Test directory listing exposure
    Send an HTTP request to http://[target]/runtime/log/ and examine whether the server returns a directory listing (a page showing file names in the log directory) without requiring authentication
    Affected if The web server returns a directory listing showing log files without any login or authentication prompt

A user is affected if NODERP version is below 6.0.2 AND the /runtime/log directory is accessible over HTTP without authentication, resulting in exposed log files.

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

Disable directory listing/indexing on the web server for the /runtime/log path, or implement proper authentication and access controls. Consider restricting network access to the application if no patch is available.

Recommended fix Moderate confidence

6.0.2

  1. 1. Back up the current NODERP installation and database before making any changes
  2. 2. Download NODERP version 6.0.2 or later from the official vendor source
  3. 3. Stop the NODERP service to prevent active sessions during upgrade
  4. 4. Replace the existing installation files with the new version
  5. 5. Ensure the /runtime/log directory is properly protected by web server configuration (deny direct access)
  6. 6. Restart the NODERP service
  7. 7. Verify the vulnerability is fixed by confirming /runtime/log is no longer externally accessible
  8. 8. Test core application functionality to ensure the upgrade did not break existing features

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

Fix this in Noderp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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