dbcve.org
Readynas OsOperating system · Netgear

CVE-2018-21160

HIGH · 8.8 CVSS v3.1 Published 2020-04-23
Fix available
A fix is available. Upgrade to 6.9.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
NETGEAR ReadyNAS devices before 6.9.3 are affected by CSRF.

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

Cross-Site Request Forgery vulnerability in NETGEAR ReadyNAS web interface versions prior to 6.9.3 allows remote attackers to trick authenticated administrators into performing unintended administrative actions via maliciously crafted requests.

MitigationUpgrade NETGEAR ReadyNAS firmware to version 6.9.3 or later to obtain the CSRF protection fix.

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
Readynas OsOperating system
Affected:>= 6.0, < 6.9.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installed ReadyNAS OS version
    Access the admin dashboard or use the command line (grep version /etc/os-release or cat /etc/version) to retrieve the firmware version
    Affected if version is 6.0 or higher but lower than 6.9.3
  2. Confirm web interface is enabled
    Check if the ReadyNAS admin web interface (port 80/443) is accessible on the device
    Affected if the web interface is exposed and the device runs a vulnerable version
  3. Verify administrative access exists
    Confirm the device has administrator accounts configured and the web interface accepts authenticated sessions
    Affected if administrators can log in to the web interface on a vulnerable firmware version

The environment is affected if the ReadyNAS OS version is 6.0 or higher but less than 6.9.3 and the web management interface is accessible to users.

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.

From vendor data
Upgrade available Upgrade to 6.9.3 or later
Fixed in 6.9.3
Interim mitigation

Upgrade NETGEAR ReadyNAS firmware to version 6.9.3 or later to obtain the CSRF protection fix.

Fix this in Readynas Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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