dbcve.org
OpensearchApplication · Amazon

CVE-2023-31141

MEDIUM · 5.9 CVSS v3.1 Published 2023-05-08
Fix available
A fix is available. Upgrade to 1.3.10 / 2.7.0 or later.
See remediation →
68/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
OpenSearch is open-source software suite for search, analytics, and observability applications. Prior to versions 1.3.10 and 2.7.0, there is an issue with the implementation of fine-grained access control rules (document-level security, field-level security and field masking) where they are not correctly applied to the queries during extremely rare race conditions potentially leading to incorrect access authorization. For this issue to be triggered, two concurrent requests need to land on the same instance exactly when query cache eviction happens, once every four hours. OpenSearch 1.3.10 and 2.7.0 contain a fix for this issue.

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

OpenSearch's fine-grained access control (document-level security, field-level security, field masking) fails to correctly apply during extremely rare race conditions when query cache eviction occurs, potentially exposing unauthorized data. The trigger requires two concurrent requests landing on the same instance precisely during cache eviction, which happens approximately once every four hours.

MitigationUpgrade OpenSearch to version 1.3.10 or 2.7.0 or later to receive the patch addressing this race condition in query cache handling.

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
OpensearchApplication
Affected:< 1.3.10>= 2.0.0, < 2.7.0
Opensearch SecurityApplication
Affected:< 1.3.10>= 2.0.0, < 2.7.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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. Check OpenSearch version
    Run `curl -s <opensearch-host>:9200/_cluster/health` or check the OpenSearch dashboard for the version number
    Affected if The installed version is less than 1.3.10, or between 2.0.0 and 2.7.0 (excluding 2.7.0)
  2. Confirm OpenSearch Security plugin is installed
    Check for the existence of the Security plugin by querying `GET _plugins/_security/api` or checking the installed plugins list
    Affected if The OpenSearch Security plugin is not installed or not functioning
  3. Verify fine-grained access control is enabled
    Check the security config at `/_plugins/_security/api/securityconfig` or review the internal users and roles configuration for DLS/FLS/masking settings
    Affected if Document-level security (DLS), field-level security (FLS), or field masking is configured on any index or role
  4. Identify exposed indices with access controls
    Review roles with `DLS` or `FLS` permissions by querying the security roles endpoint
    Affected if Any role uses document-level security, field-level security, or field masking on sensitive indices

You are affected if you run a vulnerable OpenSearch version (pre-1.3.10, or 2.0.0 to pre-2.7.0) AND have fine-grained access control (DLS/FLS/field masking) enabled on any index.

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 1.3.10 / 2.7.0 or later
Fixed in 1.3.102.7.0
Interim mitigation

Upgrade OpenSearch to version 1.3.10 or 2.7.0 or later to receive the patch addressing this race condition in query cache handling.

Recommended fix High confidence

OpenSearch 1.3.10+ (for 1.x branches) or OpenSearch 2.7.0+ (for 2.x branches)

  1. 1. Identify the current OpenSearch version running in your environment (check both OpenSearch and OpenSearch Security components)
  2. 2. If running OpenSearch 1.x (version < 1.3.10): plan upgrade to version 1.3.10 or the latest 1.3.x stable release
  3. 3. If running OpenSearch 2.x (version >= 2.0.0 and < 2.7.0): plan upgrade to version 2.7.0 or the latest 2.x stable release
  4. 4. Ensure both OpenSearch and OpenSearch Security components are upgraded together to matching fixed versions
  5. 5. Test the upgrade in a non-production environment first to verify compatibility with your existing configuration and plugins
  6. 6. Create a backup of your cluster state and configuration before upgrading
  7. 7. Apply the upgrade to production following your organization's change management process
Caveat Minor version upgrades within the same major branch typically have minimal breaking changes; however, review OpenSearch release notes for any configuration or API changes between your current version and the target version

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

Fix this in Opensearch Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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