dbcve.org
Reyee OsOperating system · Ruijienetworks

CVE-2024-48874

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-06
Fix available
A fix is available. Upgrade to 2.320.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 could give attackers the ability to force Ruijie's proxy servers to perform any request the attackers choose. Using this, attackers could access internal services used by Ruijie and their internal cloud infrastructure via AWS cloud metadata 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

This is a Server-Side Request Forgery (SSRF) vulnerability in Ruijie Reyee OS proxy servers. Attackers can craft malicious requests that force the proxy to make arbitrary HTTP requests to internal resources, including AWS cloud metadata services (169.254.169.254), potentially exposing sensitive cloud credentials and internal infrastructure.

MitigationUpgrade Ruijie Reyee OS to version 2.320.x or later. If immediate patching is not possible, restrict outbound access from proxy servers to internal networks and disable access to cloud metadata endpoints (169.254.169.254).

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
High
Availability
High

CVSS:3.1/AV:N/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 Ruijie Reyee OS installation
    Locate and access the Ruijie network device or software that runs Ruijie Reyee OS. This is typically found on Ruijie Reyee series routers, switches, or wireless controllers.
    Affected if The device or system is running Ruijie Reyee OS firmware.
  2. Determine the installed Reyee OS version
    Access the device management interface (web GUI or CLI) and navigate to the system information or firmware version section. In CLI, the command may be 'show version' or 'display version' depending on the device model.
    Affected if The installed version is >= 2.206.0 and < 2.320.0.
  3. Verify the proxy service is enabled
    Check the device configuration for proxy server settings. In the web interface, look under Network Settings, Proxy, or Forwarding settings. In CLI, use 'show running-config' or 'display current-configuration' and search for proxy-related configuration.
    Affected if The proxy feature or HTTP forwarding service is configured and enabled on the device.
  4. Confirm network accessibility to cloud metadata endpoints
    From a device behind the Ruijie proxy or from the proxy itself, attempt to reach 169.254.169.254 (AWS metadata endpoint) or check routing tables to determine if this internal IP is reachable.
    Affected if The proxy server can route traffic to 169.254.169.254 or other internal metadata addresses.

You are affected if Ruijie Reyee OS version 2.206.0 through 2.319.x is running with the proxy feature enabled and the device has network access to internal resources such as cloud metadata endpoints.

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. If immediate patching is not possible, restrict outbound access from proxy servers to internal networks and disable access to cloud metadata endpoints (169.254.169.254).

Recommended fix High confidence

2.320.0 or later

  1. Identify all Ruijie Reyee OS devices in the environment
  2. Check the current firmware version of each device running Reyee OS
  3. For devices running versions >= 2.206.0 and < 2.320.0, plan an upgrade to version 2.320.0 or later
  4. Download the firmware version 2.320.0 or later from the official Ruijie Networks support website
  5. Follow Ruijie's official upgrade procedure to apply the firmware update to affected devices
  6. After upgrading, verify that the firmware version has been successfully updated to 2.320.0 or later
  7. Confirm that the SSRF vulnerability is no longer present by validating that the device no longer makes arbitrary requests to internal or external resources

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

Fix this in Reyee Os 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 the upgrade done

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-48874 — 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-48874 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