CVE-2021-32095
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 · uneditedU.S. National Security Agency (NSA) Emissary 5.9.0 allows an authenticated user to delete arbitrary files.
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 confidenceNSA Emissary 5.9.0 contains a path traversal vulnerability allowing authenticated users to delete arbitrary files on the host system via crafted file path requests. This authenticated arbitrary file deletion could lead to denial of service, data loss, or potentially privilege escalation if critical system files are targeted.
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= 5.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Verify installed Emissary versionLocate the Emissary installation directory and check the version file, startup script, or use the admin interface version information. Common paths include /opt/emissary or the installation root directory. Run: emissary --version or check the about page in the web UI.Affected if The installed version is exactly 5.9.0
-
Confirm Emissary service is exposedCheck if the Emissary web interface or API is accessible on the network. Identify the listening port (typically 8001 for the admin interface) and verify network binding settings in the Emissary configuration.Affected if The Emissary service is accessible over the network and accepts connections
-
Identify authentication configurationReview the Emissary configuration files to determine how user authentication is handled. Check for user authentication settings, session management, and whether anonymous or default credentials are enabled.Affected if Anonymous access is allowed or weak authentication is configured, allowing unauthenticated or low-privilege access to the file deletion functionality
-
Review access logs for file deletion operationsExamine Emissary access and audit logs for DELETE requests or file operation commands with unusual path patterns. Look for sequences like ../ or absolute paths in file deletion parameters.Affected if Logs show file deletion requests with path traversal patterns or deletion of files outside expected directories
A user is affected if NSA Emissary version 5.9.0 is running and the service is accessible, particularly if authentication is weak or anonymous access is permitted.
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.
From vendor dataApply vendor patch or update to a patched version of Emissary if available. If no patch exists, restrict network access to the Emissary service to trusted authenticated users only and monitor for suspicious file deletion activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32095 — 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-2021-32095 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