dbcve.org
Jh Rvb1 FirmwareOperating system · Sharp

CVE-2024-23788

HIGH · 8.1 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 →
86/100
Remediation priority · High
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
Server-side request forgery 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 send an arbitrary HTTP request (GET) from 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

Server-side request forgery (SSRF) vulnerability in Energy Management Controller JH-RVB1/JH-RV11 allows a network-adjacent unauthenticated attacker to send arbitrary HTTP GET requests from the affected device. This can be exploited to interact with internal systems, bypass network boundaries, or exfiltrate data via the compromised device.

MitigationIsolate the affected device on a restricted network segment with strict firewall rules, and monitor for indicators of compromise. Apply vendor patches when 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
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
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify the device model on the network
    Access the device web 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 and is network-accessible
  2. Check the installed firmware version
    Log into the device admin interface and navigate to the firmware or system information page to view the current firmware version number
    Affected if The firmware version is b0.1.9.1 or lower (any version <= b0.1.9.1)
  3. Verify the HTTP management interface is exposed
    Attempt to access the device web interface on common HTTP ports (80, 8080) from a network-adjacent host to confirm the service is listening
    Affected if The device HTTP service is accessible from an untrusted network segment
  4. Review network logs for suspicious outbound HTTP requests
    Monitor network traffic or firewall logs for the device initiating HTTP GET requests to internal IP ranges, unusual external domains, or known internal services
    Affected if The device is making outbound HTTP requests to internal infrastructure without legitimate cause
  5. Check for unauthorized internal network probing
    Review intrusion detection logs or internal network monitoring for signs that the device has scanned internal systems or attempted connections to internal services
    Affected if The device shows evidence of sending arbitrary HTTP requests to internal systems

A user is affected if they have a JH-RVB1 or JH-RV11 device running firmware version b0.1.9.1 or lower that is accessible on the network and the SSRF vulnerability can be exploited to proxy requests from the device.

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

Isolate the affected device on a restricted network segment with strict firewall rules, and monitor for indicators of compromise. Apply vendor patches when available.

Recommended fix Moderate confidence

Firmware version newer than B0.1.9.1 (e.g., B0.1.9.2 or latest available)

  1. 1. Identify the specific model of your Sharp Energy Management Controller (JH-RVB1 or JH-RV11)
  2. 2. Visit the official Sharp support website (jp.sharp) or contact Sharp support to obtain the latest firmware version
  3. 3. Download the firmware update file from the official Sharp source
  4. 4. Follow the manufacturer's firmware update instructions specific to your device model
  5. 5. Verify the firmware version after updating to confirm the fix is applied
  6. 6. Ensure the device is updated to a version newer than B0.1.9.1 (e.g., B0.1.9.2 or later)
Caveat Review release notes for any functionality changes or migration requirements 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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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