AtlasApplication · Apache
CVE-2022-34271
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 · uneditedA vulnerability in import module of Apache Atlas allows an authenticated user to write to web server filesystem. This issue affects Apache Atlas versions from 0.8.4 to 2.2.0.
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 confidenceThe vulnerability in Apache Atlas's import module allows any authenticated user to write files to arbitrary locations on the web server filesystem, likely due to insufficient path traversal validation in the import functionality.
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
AtlasApplication
>= 0.8.4, <= 2.2.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
- High
- Availability
- High
CVSS:3.1/AV:N/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 Apache Atlas installation and versionLocate the Atlas installation directory and check the version file (typically in the root Atlas directory, often named 'VERSION' or check pom.xml/build files for version info). Also check the Atlas web UI footer or admin pages for version display.Affected if The installed version falls within >= 0.8.4 and <= 2.2.0
-
Verify import module is accessibleCheck if the Atlas import functionality is accessible. This typically involves the /api/atlas/v2/import endpoint. Verify whether unauthenticated or authenticated users can access the import API endpoints by reviewing Atlas authentication configuration and web.xml or equivalent security settings.Affected if The import module endpoints are accessible to authenticated users without additional restrictions
-
Check for path traversal indicators in import logsReview Atlas audit logs and application logs for import operations. Search for import requests containing path traversal patterns like '../' or absolute paths in import file parameters. Logs are typically in the 'logs' directory under the Atlas installation.Affected if Import operations with path traversal sequences are present in logs, indicating the vulnerability is exploitable
-
Review import endpoint configurationExamine the Atlas configuration files (atlas-application.properties or similar) for import-related settings. Check whether there are any restrictions on import file paths or if the import functionality allows arbitrary file paths to be specified.Affected if The import module permits arbitrary file path specification without validation
You are affected if Apache Atlas version is between 0.8.4 and 2.2.0 inclusive AND the import module is accessible to authenticated users.
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 · scopedUpgrade Apache Atlas to version 2.3.0 or later. If immediate patching is not feasible, restrict and audit access to the import module functionality.
Apache Atlas 2.3.0 or later
- Review the Apache Atlas import module configuration and ensure only authorized authenticated users have import permissions
- Plan upgrade to Apache Atlas version 2.3.0 or later which contains the fix for this path traversal vulnerability
- Before upgrading, perform a complete backup of the Atlas metadata repository and configuration files
- Test the upgrade in a non-production environment to verify compatibility with existing workflows
- After upgrading, verify that the import module no longer allows path traversal by testing with paths outside the intended import directory
- Monitor Apache Atlas release notes and security advisories for any additional patches
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Atlas
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34271 — 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-2022-34271 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