ElasticsearchDatabase / datastore · Elastic
CVE-2023-46674
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 identified that allowed the unsafe deserialization of java objects from hadoop or spark configuration properties that could have been modified by authenticated users. Elastic would like to thank Yakov Shafranovich, with Amazon Web Services for reporting 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 confidenceElastic products allowed unsafe deserialization of Java objects from Hadoop or Spark configuration properties that could be modified by authenticated users, potentially enabling remote code execution.
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
ElasticsearchDatabase / datastore
< 7.17.11>= 8.0.0, < 8.9.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Elasticsearch versionRun `curl -XGET 'localhost:9200/'` or check the elasticsearch logs/startup banner for the version numberAffected if Version is < 7.17.11 or >= 8.0.0 and < 8.9.0
-
Check if Hadoop integration is configuredLook for Hadoop-related configuration in elasticsearch.yml files or inspect cluster settings via `GET /_cluster/settings?include_defaults=true` for properties containing 'hadoop' or 'org.apache.hadoop'Affected if Hadoop configuration properties exist in the Elasticsearch configuration
-
Check if Spark integration is configuredInspect cluster settings via `GET /_cluster/settings?include_defaults=true` for properties containing 'spark' or 'org.apache.spark'Affected if Spark configuration properties exist in the Elasticsearch configuration
-
Verify user access to configuration APIsReview Elasticsearch role definitions and security settings to determine which authenticated users can access the APIs that modify Hadoop or Spark configuration properties (typically via PUT/POST to _cluster/settings or ingest pipeline settings)Affected if Authenticated users have write access to modify Hadoop or Spark configuration properties without restricted review
You are affected if your Elasticsearch version falls within the vulnerable ranges AND Hadoop or Spark integration is enabled with users able to modify their configuration properties.
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 · scoped7.17.118.9.0
Update Elastic products to the patched version as specified in the security advisory. If immediate patching is not possible, restrict or audit write access to Hadoop/Spark configuration properties for authenticated users.
7.17.11 (7.x branch) or 8.9.0 (8.x branch)
- Backup your Elasticsearch cluster data and configuration before upgrading.
- Review the Elasticsearch upgrade documentation at https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html
- For Elasticsearch 7.x: Upgrade to version 7.17.11 or later
- For Elasticsearch 8.x: Upgrade to version 8.9.0 or later
- After upgrading, verify that the cluster is healthy and all nodes have joined successfully using the _cluster/health API
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Elasticsearch
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46674 — 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-46674 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