Missing AuthenticationWeakness · CWE-306

CVE-2025-0456

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The airPASS from NetVision Information has a Missing Authentication vulnerability, allowing unauthenticated remote attackers to access the specific administrative functionality to retrieve * all accounts and passwords.

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

airPASS from NetVision Information has a critical missing authentication vulnerability that allows unauthenticated remote attackers to access specific administrative functionality without any credentials. This exposes all user accounts and their passwords, enabling full account enumeration and potential account takeover.

MitigationImplement proper authentication and authorization checks for all administrative endpoints. Additionally, ensure passwords are properly hashed if not already, and conduct a comprehensive security review to identify any other unprotected administrative functions.

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
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. Identify if airPASS is installed
    Search the system or web server for airPASS application files, or check running services that may host the NetVision airPASS application
    Affected if airPASS from NetVision Information is present on the system
  2. Determine airPASS version
    Check the application version information typically found in the software itself, configuration files, or about/ status pages within the airPASS application
    Affected if The installed version matches any version of airPASS from NetVision (no specific version range provided)
  3. Locate the administrative endpoint
    Identify the specific administrative function or endpoint within airPASS that handles user account data retrieval. Check web server access logs or application routing configuration for paths related to user credentials, admin functions, or account exports
    Affected if The endpoint exists and is accessible without requiring authentication
  4. Test endpoint authentication
    Send an HTTP request to the identified administrative endpoint without providing any authentication credentials (no session cookie, no API key, no Basic Auth)
    Affected if The endpoint returns user account credentials (usernames and passwords) without requiring any authentication

A user is affected if the airPASS application is installed and the administrative endpoint that exposes user credentials is accessible without any authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks for all administrative endpoints. Additionally, ensure passwords are properly hashed if not already, and conduct a comprehensive security review to identify any other unprotected administrative functions.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0456 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0456 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