dbcve.org
Jh Rvb1 FirmwareOperating system · Sharp

CVE-2024-23786

CRITICAL · 9.3 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 →
100/100
Remediation priority · Urgent
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 scripting 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 execute an arbitrary script on the web browser of the user who is accessing 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 confidence

A stored cross-site scripting (XSS) vulnerability exists in the web management interface of the Energy Management Controller JH-RVB1/JH-RV11 (firmware B0.1.9.1 and earlier). An unauthenticated attacker with network adjacency can inject malicious JavaScript that executes in the browsers of users accessing the management page.

MitigationApply available firmware updates to resolve the vulnerability. As a compensating control, restrict network access to the management interface using network segmentation and ACLs to limit exposure to only trusted administrative users.

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
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
    Access the web management interface of the Energy Management Controller and locate the device information or system status page to confirm the model is JH-RVB1 or JH-RV11
    Affected if The device model is Sharp JH-RVB1 or JH-RVB11
  2. Check the installed firmware version
    In the web management interface, navigate to the firmware or system information section and note the firmware version number
    Affected if The firmware version is B0.1.9.1 or earlier (any version up to and including B0.1.9.1)
  3. Confirm web management interface is accessible
    Verify that the web management interface is reachable over the network on the expected IP address or hostname
    Affected if The web management interface is exposed on the network (the vulnerability allows unauthenticated injection, so exposure alone indicates potential exploitability)
  4. Inspect input fields for potential XSS injection points
    Examine the web management interface forms and input fields (such as device name, configuration fields, or user-profile settings) for any existing malicious script payloads
    Affected if Malicious JavaScript code is already present in any stored parameter or field within the management interface

A user is affected if the device is a JH-RVB1 or JH-RV11 model running firmware version B0.1.9.1 or earlier, and the web management interface is network-accessible.

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 available firmware updates to resolve the vulnerability. As a compensating control, restrict network access to the management interface using network segmentation and ACLs to limit exposure to only trusted administrative users.

Recommended fix Moderate confidence

Firmware version greater than B0.1.9.1 (contact Sharp for specific fixed release number)

  1. Identify the exact model number (JH-RVB1 or JH-RV11) of the affected Energy Management Controller device
  2. Access the device's administrative interface or documentation to verify the current firmware version
  3. Navigate to the official Sharp support website (jp.sharp) or contact Sharp technical support to obtain the firmware update
  4. Follow Sharp's official firmware update procedure to upgrade to a version newer than B0.1.9.1
  5. After updating, verify the firmware version has been successfully changed and the management interface is accessible
  6. Confirm the XSS vulnerability is resolved by checking release notes or contacting Sharp support
Caveat Review firmware update documentation for any required reconfiguration or compatibility considerations before applying update

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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