CVE-2025-66954
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 · uneditedA vulnerability exists in the Buffalo Link Station version 1.85-0.01 that allows unauthenticated or guest-level users to enumerate valid usernames and their associated privilege roles. The issue is triggered by modifying a parameter within requests sent to the /nasapi endpoint.
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 confidenceThe Buffalo Link Station firmware 1.85-0.01 has an information disclosure vulnerability in the /nasapi endpoint where unauthenticated or guest-level users can manipulate a request parameter to enumerate valid usernames and their associated privilege roles. This allows an attacker to gather valid user accounts for further attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm Buffalo Link Station firmware versionAccess the device administration interface or check the firmware version via the system settings page. Alternatively, use the command line or API if available to query the firmware version.Affected if The installed firmware version is 1.85-0.01 or falls within the affected range.
-
Verify /nasapi endpoint accessibilityAttempt to access the /nasapi endpoint via HTTP/HTTPS from the network. This can be done using curl or a browser request to http://[device-ip]/nasapi.Affected if The endpoint is reachable and responds to requests without requiring authentication.
-
Test for user enumeration without authenticationSend a request to the /nasapi endpoint with manipulated parameters (such as an empty or modified user field) as an unauthenticated user or guest-level session. Observe if the response includes valid usernames and privilege role information.Affected if The endpoint returns valid user accounts and their associated privilege roles without requiring authentication.
-
Check if guest accounts can access sensitive user dataLog in with a guest-level account (if enabled) and attempt to access the /nasapi endpoint to query user information. Compare the response to what an unauthenticated request returns.Affected if Guest-level users can retrieve user account enumeration data through the API.
You are affected if your Buffalo Link Station runs firmware 1.85-0.01 and the /nasapi endpoint is accessible to unauthenticated or guest users, allowing them to enumerate valid usernames and privilege roles.
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 dataRestrict access to the /nasapi endpoint by implementing proper authentication and authorization checks; require authenticated sessions with appropriate privileges before returning user account information. If a patch is available from Buffalo, apply it promptly.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66954 — 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-66954 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