dbcve.org
Reyee OsOperating system · Ruijienetworks

CVE-2024-42494

HIGH · 7.5 CVSS v3.1 Published 2024-12-06
Fix available
A fix is available. Upgrade to 2.320.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x contains a a feature that could enable sub accounts or attackers to view and exfiltrate sensitive information from all cloud accounts registered to Ruijie's services

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

Ruijie Reyee OS versions 2.206.x through 2.319.x contains a vulnerable feature that allows authenticated sub-accounts or attackers to bypass access controls and view or exfiltrate sensitive information from all cloud accounts registered to Ruijie's services. This is a broken access control vulnerability affecting the multi-tenant cloud infrastructure.

MitigationUpgrade Ruijie Reyee OS to version 2.320.x or later to remediate this access control vulnerability.

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
Reyee OsOperating system
Affected:>= 2.206.0, < 2.320.0

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

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Ruijie Reyee OS version
    Access the device management interface or use the command line interface (CLI) to retrieve the firmware version. This is typically found in the system information or device status page. Compare the version number against the affected range: >= 2.206.0 and < 2.320.0.
    Affected if The installed version falls within 2.206.x through 2.319.x inclusive.
  2. Confirm cloud management feature is enabled
    Log into the Ruijie device web interface or CLI and check whether the cloud management or Ruijie Cloud connection feature is activated. This is usually found under Cloud Settings, Cloud Management, or similar network service configuration menus.
    Affected if Cloud management or Ruijie Cloud integration is enabled and the device is registered to Ruijie's cloud services.
  3. Verify presence of sub-accounts
    Access the cloud account management section (typically in the Ruijie Cloud portal or device user management interface) and check if multiple user accounts or sub-accounts have been created beyond the primary administrator account.
    Affected if Multiple user accounts or sub-accounts exist in the cloud management system.
  4. Check account isolation settings
    In the Ruijie Cloud portal, examine whether there are configurations that control cross-account data access or tenant isolation within the multi-tenant cloud infrastructure.
    Affected if Account isolation controls are absent, misconfigured, or the interface allows viewing data from other cloud accounts.

If the Ruijie Reyee OS version is between 2.206.0 and 2.319.x and the cloud management feature with sub-accounts is in use, the environment is vulnerable to cross-account data access.

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
Upgrade available Upgrade to 2.320.0 or later
Fixed in 2.320.0
Interim mitigation

Upgrade Ruijie Reyee OS to version 2.320.x or later to remediate this access control vulnerability.

Recommended fix High confidence

Reyee OS version 2.320.0 or later

  1. 1. Access the Ruijie Reyee OS management interface or controller
  2. 2. Navigate to System Settings or Firmware Management
  3. 3. Check current firmware version to confirm it is between 2.206.0 and 2.319.x
  4. 4. Download firmware version 2.320.0 or later from Ruijie's official support portal
  5. 5. Upload the new firmware file to the device or controller
  6. 6. Apply the firmware upgrade following vendor-provided instructions
  7. 7. After upgrade, verify the new version is 2.320.0 or higher
  8. 8. Confirm the vulnerability is resolved by testing that sub-accounts can no longer access data from other cloud accounts
Caveat Review release notes for any configuration or feature changes between your current version and 2.320.0; some legacy features may be deprecated

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

Fix this in Reyee Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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