dbcve.org
Jh Rvb1 FirmwareOperating system · Sharp

CVE-2024-23785

MEDIUM · 6.5 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 →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site request forgery vulnerability in Energy Management Controller with Cloud Services JH-RVB1 /JH-RV11 Ver.B0.1.9.1 and earlier allows a remote unauthenticated attacker to change the product settings.

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

Cross-site request forgery (CSRF) vulnerability in Energy Management Controller JH-RVB1/JH-RV11 firmware B0.1.9.1 and earlier allows a remote unauthenticated attacker to induce authenticated users to unknowingly submit malicious requests that change device settings.

MitigationApply vendor firmware update when available; otherwise implement network segmentation to isolate the device and use referrer validation/anti-CSRF tokens if the web interface supports custom configuration.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
    Locate the Energy Management Controller device and confirm it is either the JH-RVB1 or JH-RV11 model. Check the device label, documentation, or web interface for the exact model number.
    Affected if The device is a Sharp JH-RVB1 or JH-RV11 model.
  2. Determine the installed firmware version
    Access the device web interface and navigate to the firmware or system information page. Note the firmware version displayed (for example, B0.1.9.1). If you have CLI access, use the appropriate command to retrieve the firmware version.
    Affected if The firmware version is B0.1.9.1 or earlier.
  3. Verify web interface accessibility
    Confirm whether the device web management interface is reachable over the network from systems other than the device itself. Attempt to access the device IP from a remote workstation browser.
    Affected if The web interface is accessible from network segments where authenticated users operate.
  4. Check if users are authenticated to the device
    Determine whether any users have active sessions or credentials that allow them to log into the device web interface. Review authentication logs if available.
    Affected if Authenticated users access the device web interface from vulnerable network positions.

A user is affected if they have a JH-RVB1 or JH-RV11 device running firmware B0.1.9.1 or earlier, with the web interface exposed to network segments where authenticated users operate.

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; otherwise implement network segmentation to isolate the device and use referrer validation/anti-CSRF tokens if the web interface supports custom configuration.

Recommended fix Moderate confidence

Firmware version > B0.1.9.1 (contact Sharp for exact fixed version)

  1. 1. Identify the current firmware version of the Jh Rvb1 or Jh Rv11 device
  2. 2. Navigate to the official Sharp support page (jp.sharp) or JVN (jvn.jp) to obtain the firmware update
  3. 3. Download the firmware version newer than B0.1.9.1
  4. 4. Follow Sharp's official firmware update procedure for the Energy Management Controller JH-RVB1/JH-RV11
  5. 5. Verify the firmware has been successfully updated by checking the device version information
Caveat Review 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
  • 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-23785 — 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-23785 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