CVE-2023-46666
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 · uneditedAn issue was discovered when using Document Level Security and the SPO "Limited Access" functionality in Elastic Sharepoint Online Python Connector. If a user is assigned limited access permissions to an item on a Sharepoint site then that user would have read permissions to all content on the Sharepoint site through Elasticsearch.
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 confidenceThe Elastic SharePoint Online Python Connector incorrectly handles Document Level Security (DLS) when users have 'Limited Access' permissions in SharePoint Online. The connector fails to properly restrict access, granting these users read permissions to ALL content on the SharePoint site through Elasticsearch, rather than limiting them to only the specific items they are authorized to access.
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< 8.10.3.0CVSS 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.
-
Identify connector versionLocate the installed Elastic SharePoint Online Python Connector and retrieve its version number. This is typically found in the connector's configuration, deployment manifest, or package metadata. Compare the version against the affected range: versions prior to 8.10.3.0 are vulnerable.Affected if The installed version is below 8.10.3.0
-
Confirm Document Level Security is enabledInspect the connector configuration for the Document Level Security (DLS) setting. DLS is typically a configuration flag or policy that controls whether access controls are applied to indexed content. Check if DLS is turned on or configured for the SharePoint Online connector.Affected if Document Level Security (DLS) is enabled in the connector configuration
-
Verify SharePoint Online target and permission modelConfirm the connector is configured to sync from a SharePoint Online environment. Check if the SharePoint site(s) being indexed utilize the 'Limited Access' permission level, which is a special permission in SharePoint Online that allows users to access specific items or libraries without seeing the entire site.Affected if The connector targets SharePoint Online and the source site contains users with 'Limited Access' permissions
You are affected if your Elastic SharePoint Online Python Connector version is below 8.10.3.0, Document Level Security is enabled, and your SharePoint Online environment includes users granted 'Limited Access' permissions, as these users could gain unintended read access to all site content.
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.
dbcve · scoped8.10.3.0
Update the Document Level Security implementation in the SharePoint Online connector to properly recognize and restrict 'Limited Access' permissions, ensuring users only receive access to content they are explicitly authorized to view.
8.10.3.0
- Identify the current version of the Elastic Sharepoint Online Python Connector in use
- Stop any services or processes currently running the connector
- Upgrade the connector to version 8.10.3.0 or later using the standard Elastic upgrade procedure
- Verify the new version is installed correctly by checking the connector version
- Restart the connector services
- Confirm that Document Level Security with SPO Limited Access now properly restricts user access to only authorized items
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46666 — 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-2023-46666 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