CVE-2024-23787
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 · uneditedPath traversal vulnerability in Energy Management Controller with Cloud Services JH-RVB1 /JH-RV11 Ver.B0.1.9.1 and earlier allows a network-adjacent unauthenticated attacker to obtain an arbitrary file in the affected product.
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 confidenceA path traversal vulnerability in the Energy Management Controller JH-RVB1/JH-RV11 allows an unauthenticated, network-adjacent attacker to read arbitrary files from the device's filesystem. The vulnerability stems from insufficient input validation in file access operations, enabling attackers to use traversal sequences (e.g., ../../../) to access files outside the intended web root or application directory.
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<= b0.1.9.1<= b0.1.9.1CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the device physical label or access the device's web management interface to confirm the model number is either JH-RVB1 or JH-RV11.Affected if Device is not JH-RVB1 or JH-RV11 - not affected by this specific CVE
-
Determine the installed firmware versionAccess the device's web administration panel (typically via HTTP/HTTPS to the device's IP address) and navigate to the System Information, Status, or About page to view the firmware version string.Affected if Unable to retrieve firmware version - further investigation needed
-
Compare firmware version against affected rangeMatch the displayed firmware version to the affected versions: <= b0.1.9.1 for both JH-RVB1 and JH-RV11 models.Affected if Firmware version is b0.1.9.1 or lower - device is affected by the path traversal vulnerability
-
Verify web interface is accessibleConfirm the device's web management interface is reachable on the network (HTTP/HTTPS ports 80/443 or configured alternate port).Affected if Web interface is not accessible - attacker cannot exploit the vulnerability remotely, though local access could still pose a risk
-
Assess network exposureDetermine if the device management interface is accessible from untrusted network segments or the public internet, as the vulnerability requires network-adjacent attacker access.Affected if Device is exposed to untrusted networks - higher risk of exploitation
If the device is a JH-RVB1 or JH-RV11 running firmware version b0.1.9.1 or lower AND the web management interface is network-accessible, the environment is affected by CVE-2024-23787.
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 dataApply the vendor-supplied firmware update to version B0.1.9.2 or later. If update unavailable, restrict network access to the device's management interface and disable unnecessary services to limit attack surface.
- 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-23787 — 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-23787 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