CVE-2024-23784
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 · uneditedImproper access control vulnerability exists in Energy Management Controller with Cloud Services JH-RVB1 /JH-RV11 Ver.B0.1.9.1 and earlier, which may allow a network-adjacent unauthenticated attacker to obtain a username and its hashed password displayed on the management page of 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 confidenceImproper access control in the Energy Management Controller's web management interface allows any network-adjacent unauthenticated user to access the management page and view stored username and hashed password credentials. This is a classic authentication bypass where the sensitive management page lacks proper access control 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<= 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 Energy Management Controller device and verify it is a Sharp Jh Rvb1 or Sharp Jh Rv11 model. Check the physical device label or the admin interface for the model number.Affected if The device is a Sharp Jh Rvb1 or Sharp Jh Rv11 model
-
Check the firmware versionAccess the web management interface or device settings to find the firmware version. Compare it against the affected version b0.1.9.1 - versions <= b0.1.9.1 are vulnerable.Affected if Firmware version is b0.1.9.1 or earlier on a Sharp Jh Rvb1 or Jh Rv11 device
-
Test unauthenticated management page accessFrom a network-adjacent machine, attempt to access the Energy Management Controller web management page directly without providing any login credentials. Observe whether the interface loads and displays content.Affected if The management page loads and displays content without requiring authentication
-
Check for credential exposureOn the unauthenticated management page (if accessible), look for any sections that display stored usernames, user accounts, or password fields. Note whether hashed password credentials are visible.Affected if Stored usernames and hashed password credentials are visible without authentication
The environment is affected if it uses a Sharp Jh Rvb1 or Jh Rv11 Energy Management Controller with firmware version b0.1.9.1 or earlier, where the web management interface is accessible without authentication and exposes stored credential data.
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 proper authentication and session validation for all management interface pages. Ensure the management page verifies user identity before displaying any sensitive information, and restrict access to only authenticated, authorized users.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23784 — 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-23784 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