dbcve.org
Jh Rvb1 FirmwareOperating system · Sharp

CVE-2024-23789

HIGH · 8.8 CVSS v3.1 Published 2024-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
Energy Management Controller with Cloud Services JH-RVB1 /JH-RV11 Ver.B0.1.9.1 and earlier allows a network-adjacent unauthenticated attacker to execute an arbitrary OS command on 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 · high confidence

Command injection vulnerability in Energy Management Controller JH-RVB1/JH-RV11 allows a network-adjacent unauthenticated attacker to execute arbitrary OS commands on the affected device. The attacker does not require authentication and only needs network adjacency to the device.

MitigationApply vendor firmware update when available. Until then, isolate affected devices on a restricted network segment, implement firewall rules to limit access to authorized personnel only, and disable external network exposure.

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
Jh Rvb1 FirmwareOperating system
Affected:<= b0.1.9.1
Jh Rv11 FirmwareOperating system
Affected:<= b0.1.9.1

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 the device model
    Access the device's web administration interface or check the device label/metadata to confirm the model is JH-RVB1 or JH-RV11
    Affected if The device model is Sharp JH-RVB1 or JH-RV11
  2. Determine installed firmware version
    Log into the device's web interface or CLI and locate the firmware version information, typically found in System Info, About, or Status pages
    Affected if The firmware version is b0.1.9.1 or earlier
  3. Verify Energy Management Controller is accessible
    Check if the Energy Management Controller service port or web endpoint is exposed and reachable from the network using tools like nmap or curl to probe common HTTP/HTTPS ports
    Affected if The Energy Management Controller interface is network-accessible without authentication
  4. Confirm network adjacency exposure
    Determine if the device is on a network segment accessible to untrusted users or systems by reviewing network topology, firewall rules, and VLAN configuration
    Affected if The device is on a network segment accessible to unauthenticated network attackers

You are affected if the device is a JH-RVB1 or JH-RV11 with firmware b0.1.9.1 or earlier and the Energy Management Controller service is network-accessible to unauthenticated adjacent attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update when available. Until then, isolate affected devices on a restricted network segment, implement firewall rules to limit access to authorized personnel only, and disable external network exposure.

Recommended fix Moderate confidence

Sharp JH-RVB1/JH-RV11 firmware version later than B0.1.9.1 (check jp.sharp for the exact fixed release number)

  1. Check the current firmware version of the JH-RVB1 or JH-RV11 device
  2. Visit the official Sharp support page (jp.sharp) or JVN (jvn.jp) to obtain the latest firmware version
  3. Download the firmware update file from the official Sharp source
  4. Follow the manufacturer-provided firmware upgrade instructions specific to the JH-RVB1/JH-RV11 device
  5. After upgrading, verify the firmware version has been updated to confirm the patch was applied
Caveat Review Sharp's firmware release notes for any configuration or compatibility changes before upgrading

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

Fix this in Jh Rvb1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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