dbcve.org
Network Drive ConnectorApplication · Elastic

CVE-2024-23447

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 8.12.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An issue was discovered in the Windows Network Drive Connector when using Document Level Security to assign permissions to a file, with explicit allow write and deny read. Although the document is not accessible to the user in Network Drive it is visible in search applications to the user.

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

The Windows Network Drive Connector has an information disclosure vulnerability in its Document Level Security feature. When permissions are set with explicit allow write and deny read, the document is correctly hidden from direct access in the Network Drive interface but remains visible in search applications, allowing unauthorized users to discover the document's existence and metadata.

MitigationApply vendor patches when available; in the interim, consider disabling or restricting search indexing for documents using Document Level Security until the fix is deployed.

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
Network Drive ConnectorApplication
Affected:< 8.12.1

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 checks

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

  1. Identify Elastic Network Drive Connector installation
    Locate the Elastic Network Drive Connector application on the Windows system and determine its version number from the application properties, installation directory, or installed programs list
    Affected if The application is installed and the version is lower than 8.12.1
  2. Verify Document Level Security feature is enabled
    Check the Network Drive Connector configuration settings or administrative console for Document Level Security settings
    Affected if Document Level Security is enabled and configured with permission rules
  3. Identify permission rules with deny read configurations
    Review the Document Level Security permission rules configured for shared drives or folders; look for rules specifying explicit allow write combined with deny read on the same documents or folders
    Affected if Permission rules exist that grant write access while denying read access on any documents or folders
  4. Confirm search indexing is active for the affected drive
    Check if Windows Search, Elasticsearch indexing, or any third-party search indexing service is enabled and scanning the Network Drive Connector mapped drives or folders
    Affected if Search indexing is enabled and the indexed location contains documents with the vulnerable permission configuration

The environment is affected if Elastic Network Drive Connector version is below 8.12.1 AND Document Level Security is used with explicit allow-write/deny-read permissions while search indexing remains enabled for those documents.

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 8.12.1 or later
Fixed in 8.12.1
Interim mitigation

Apply vendor patches when available; in the interim, consider disabling or restricting search indexing for documents using Document Level Security until the fix is deployed.

Recommended fix High confidence

Elastic Stack 8.12.1 (Network Drive Connector 8.12.1)

  1. 1. Back up your Elasticsearch cluster and any custom configurations
  2. 2. Review the Elastic Stack Upgrade Guide at https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html
  3. 3. Ensure your system meets the prerequisites for version 8.12.1
  4. 4. Plan a maintenance window as upgrade will require cluster restart
  5. 5. Perform a rolling upgrade or full cluster upgrade to Elastic Stack version 8.12.1
  6. 6. Verify that the Network Drive Connector version is updated to match 8.12.1
  7. 7. Test Document Level Security functionality to confirm the access control issue is resolved
  8. 8. Monitor logs for any errors related to the Network Drive Connector after upgrade
Caveat Elasticsearch 8.x upgrades may have breaking changes; review the release notes for 8.12.1 for any known issues, particularly around security features and network connector configurations

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

Fix this in Network Drive Connector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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