CVE-2024-47043
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 · uneditedRuijie Reyee OS versions 2.206.x up to but not including 2.320.x could enable an attacker to correlate a device serial number and the user's phone number and part of the email address.
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 confidenceRuijie Reyee OS versions 2.206.x through 2.319.x contain an information disclosure vulnerability that allows an attacker to correlate device serial numbers with user personal information (phone numbers and partial email addresses). This is likely due to improper access controls or information leakage in the device registration or management interface.
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>= 2.206.0, < 2.320.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ruijie Reyee OS versionAccess the device management interface or use the command line interface (CLI) to retrieve the OS version. Typically done via 'show version' command in CLI or checking the system info page in the web UI.Affected if The installed version is 2.206.0 through 2.319.x (any version >= 2.206.0 but < 2.320.0)
-
Verify if the device registration or management portal is accessibleDetermine if the Ruijie Reyee management web interface or registration portal is exposed to network access. Check the HTTP/HTTPS accessibility of the device from external interfaces using a browser or network scan.Affected if The management or registration interface is reachable from untrusted networks (especially the internet)
-
Review API responses from the registration endpointIf you have access to logs or can test the registration API, send requests to the device registration endpoint and inspect responses for unexpected information leakage. Look for responses that may expose user personal data (phone numbers, email addresses) alongside device serial numbers.Affected if The API returns user personal information (phone numbers or partial email addresses) in response to requests that should not reveal such data
Your environment is affected if the installed Ruijie Reyee OS version falls within 2.206.0 to 2.319.x and the management or registration interface is accessible, allowing correlation of serial numbers with personal user data.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.320.0
Upgrade Ruijie Reyee OS to version 2.320.x or later to remediate this vulnerability.
Reyee OS 2.320.0 or later
- Identify the current Reyee OS version running on the device
- Confirm the version is >= 2.206.0 and < 2.320.0
- Upgrade the Reyee OS firmware to version 2.320.0 or later
- After upgrade, verify the device is running a secure version (2.320.0 or later)
- Test that normal device functionality remains intact after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47043 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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