CVE-2025-56087
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 · uneditedOS Command Injection vulnerability in Ruijie RG-BCR RG-BCR600W allowing attackers to execute arbitrary commands via a crafted POST request to the run_tcpdump in file /usr/lib/lua/luci/controller/admin/common_tcpdump.lua.
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 confidenceOS Command Injection vulnerability in Ruijie RG-BCR600W routers where the run_tcpdump function in /usr/lib/lua/luci/controller/admin/common_tcpdump.lua does not properly sanitize user input from POST requests, allowing authenticated attackers to execute arbitrary OS commands on the device.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Ruijie RG-BCR600WAccess the router web interface or check the device label/menu for the exact model number. Alternatively, use nmap or check DHCP fingerprints to identify the device on the network.Affected if The device is a Ruijie RG-BCR600W router - all firmware versions of this model are affected.
-
Verify the vulnerable Lua file existsAccess the router via SSH or telnet (if enabled) and check for the presence of /usr/lib/lua/luci/controller/admin/common_tcpdump.lua. If you can browse the firmware image, extract and search for this file path.Affected if The file /usr/lib/lua/luci/controller/admin/common_tcpdump.lua exists on the device, indicating the vulnerable code is present.
-
Check if the admin interface is network-accessibleDetermine if the router web management interface (typically ports 80/443) is exposed to untrusted networks. Use a browser or curl to access the admin login page from an external IP. Review firewall rules and port forwarding configurations.Affected if The admin interface is reachable from untrusted networks (WAN/Internet), increasing exposure to authenticated attackers.
-
Assess authentication controls on the tcpdump endpointLog into the admin interface and navigate to any tcpdump or packet capture features. Verify whether the common_tcpdump.lua controller requires strong authentication and whether session tokens are properly validated.Affected if The tcpdump function in common_tcpdump.lua can be accessed without proper authentication enforcement or uses predictable session handling.
-
Look for signs of command injection exploitationReview router system logs (/var/log/ messages) and web server logs for suspicious commands, unusual shell invocations, or unexpected network traffic to the admin interface. Check for new user accounts or modified configurations.Affected if Logs show unexpected command execution, shell history anomalies, or unauthorized configuration changes consistent with command injection.
A user is affected if they operate a Ruijie RG-BCR600W router with the common_tcpdump.lua file present and the admin interface accessible to potential authenticated attackers.
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.
From vendor dataApply available firmware patches from Ruijie Networks; if no patch exists, disable the affected tcpdump administrative function at the network edge or implement strict access controls to limit exposure to authorized management personnel only.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56087 — 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-2025-56087 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