dbcve.org
Reyee OsOperating system · Ruijienetworks

CVE-2024-47547

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 contains a weak mechanism for its users to change their passwords which leaves authentication vulnerable to brute force attacks.

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

Ruijie Reyee OS versions 2.206.x through 2.319.x contain a weak password change mechanism that fails to properly protect authentication, making the system vulnerable to brute force attacks. This critical flaw in the password modification process allows attackers to potentially compromise user credentials through repeated authentication attempts.

MitigationUpgrade Ruijie Reyee OS to version 2.320.x or later to remediate the weak password change mechanism vulnerability. If immediate patching is not possible, implement network-level rate limiting and brute force detection on authentication endpoints.

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. Check Ruijie Reyee OS version
    Access the router's web management interface and navigate to System Settings > Device Info, or use the CLI command 'show version' to retrieve the firmware version number
    Affected if Installed version is >= 2.206.0 and < 2.320.0
  2. Verify web management interface is accessible
    Confirm the router's web interface is reachable on the network (typically ports 80, 443, or 8080) - check if HTTP/HTTPS responses are received from the device
    Affected if Web interface is exposed and version falls within the affected range
  3. Test password change endpoint for rate limiting
    Send multiple rapid password change requests to the password change API endpoint (commonly /cgi-bin/luci/api/auth or similar) using a tool like curl or Burp Suite, observing whether any rate limiting, account lockout, or CAPTCHA is triggered
    Affected if Multiple password change attempts complete without any protection mechanism (no rate limiting, no lockout, no CAPTCHA)
  4. Confirm brute force protection is absent
    Send sequential password change requests with different usernames or from the same source IP, checking if the system allows unlimited attempts without blocking or throttling
    Affected if System permits unlimited password change attempts without any defensive measures

Environment is affected if Ruijie Reyee OS version is 2.206.0 through 2.319.x and the web-based password change functionality is accessible without rate limiting, account lockout, or CAPTCHA protections in place.

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 the weak password change mechanism vulnerability. If immediate patching is not possible, implement network-level rate limiting and brute force detection on authentication endpoints.

Recommended fix High confidence

2.320.0 or later

  1. Check current Reyee OS version via web interface or CLI
  2. Download firmware version 2.320.0 or later from official Ruijie support channels
  3. Apply firmware upgrade through Reyee OS management interface or CLI following vendor documentation
  4. Verify upgrade to version 2.320.0 or later was successful
  5. Confirm the weak password recovery mechanism vulnerability is remediated

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