dbcve.org
Blue Xp ConnectorApplication · Netapp

CVE-2023-27311

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-26
Fix available
A fix is available. Upgrade to 3.9.25 or later.
See remediation →
62/100
Remediation priority · Elevated
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
NetApp Blue XP Connector versions prior to 3.9.25 expose information via a directory listing. A new Connector architecture resolves this issue - obtaining the fix requires redeploying a fresh Connector.

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 confidence

NetApp Blue XP Connector versions prior to 3.9.25 contain a directory listing vulnerability that exposes sensitive file system information to unauthenticated users. This information disclosure occurs through improper access controls on the web server, allowing attackers to enumerate directory contents.

MitigationUpgrade to Blue XP Connector version 3.9.25 or later. The fix requires redeploying a fresh Connector with the new architecture rather than an in-place upgrade.

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
Blue Xp ConnectorApplication
Affected:< 3.9.25

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Blue XP Connector is deployed
    Identify any systems running NetApp Blue XP Connector in your environment. Check for Connector virtual machines, containers, or cloud deployments.
    Affected if Blue XP Connector is installed in the environment
  2. Determine installed Connector version
    Access the Connector management interface or check the Connector system information to identify the current version number.
    Affected if The version is lower than 3.9.25 (for example, 3.9.24 or earlier)
  3. Check for exposed web interface
    Locate the URL or IP address used to access the Blue XP Connector web interface and verify it is reachable from your network.
    Affected if The Connector web interface is accessible over the network
  4. Test for directory listing exposure
    Attempt to access common directory paths on the Connector web server (for example, appending / or common subdirectory names to the Connector URL) to see if directory contents are displayed without authentication.
    Affected if Directory contents are displayed without requiring authentication
  5. Verify access control configuration
    Review the Connector web server or proxy configuration for access control rules. Confirm whether unauthenticated users can access directory listings.
    Affected if Unauthenticated directory enumeration is possible due to missing or improper access controls

You are affected if Blue XP Connector version 3.9.24 or earlier is deployed and its web server exposes directory listings to unauthenticated 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.

dbcve · scoped
Upgrade available Upgrade to 3.9.25 or later
Fixed in 3.9.25
Interim mitigation

Upgrade to Blue XP Connector version 3.9.25 or later. The fix requires redeploying a fresh Connector with the new architecture rather than an in-place upgrade.

Recommended fix High confidence

Blue XP Connector 3.9.25 or later (fresh deployment)

  1. Review the existing Blue XP Connector configuration and document current settings, policies, and integrations
  2. Stop or decommission the existing Blue XP Connector instance running a version prior to 3.9.25
  3. Deploy a fresh Blue XP Connector instance using version 3.9.25 or later from the NetApp Blue XP console or deployment mechanism
  4. Configure the new Connector with the same settings, cloud provider connections, and integrations as the previous instance
  5. Verify that the new Connector is operational and successfully communicating with Blue XP services
  6. Confirm that directory listing vulnerability is resolved by testing access paths
Caveat This fix requires redeploying a fresh Connector instance - it is not an in-place upgrade; configuration must be reapplied to the new deployment and there will be downtime during the transition

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Blue Xp Connector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

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