CVE-2023-3722
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 OS command injection vulnerability was found in the Avaya Aura Device Services Web application which could allow remote code execution as the Web server user via a malicious uploaded file. This issue affects Avaya Aura Device Services version 8.1.4.0 and earlier.
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 confidenceOS command injection vulnerability in Avaya Aura Device Services Web application's file upload functionality allows remote attackers to execute arbitrary OS commands as the web server user by uploading specially crafted malicious files. The vulnerability is exploitable remotely without authentication due to insufficient input sanitization on uploaded files.
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.1.4.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Avaya Aura Device Services installationLocate the Avaya Aura Device Services software on the system. Check for running processes named 'DeviceServices' or related services, or look for the web application typically hosted on ports 8080 or 8443.Affected if The software is found running on the system
-
Determine the installed versionAccess the Avaya Aura Device Services web interface or check the software version through its administrative console. The version is typically displayed in the About or System Information section of the management interface.Affected if The installed version is 8.1.4.0 or lower
-
Verify file upload functionality is enabledAccess the Avaya Aura Device Services web interface and navigate to the file upload feature in the administration or configuration sections. Check if the upload functionality is accessible and not explicitly disabled.Affected if File upload functionality is accessible and enabled in the web interface
-
Assess network accessibility of the device services interfaceDetermine if the Avaya Aura Device Services web interface (typically ports 8080 or 8443) is reachable from network locations outside the trusted internal network. Use network scanning or firewall rules review to confirm exposure.Affected if The device services web interface is accessible from untrusted or external networks without proper access controls
A system is affected if Avaya Aura Device Services version 8.1.4.0 or lower is installed with its web interface and file upload feature accessible, especially if exposed to untrusted networks.
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 Avaya Aura Device Services to a version beyond 8.1.4.0 when the patch becomes available. Until then, restrict network access to the device services interface and implement additional file upload validation at network perimeter.
Contact Avaya for the specific fixed release (version higher than 8.1.4.0)
- 1. Identify all Avaya Aura Device Services installations in the environment running version 8.1.4.0 or earlier.
- 2. Restrict or disable file upload functionality at the network level (e.g., via WAF, firewall rules) as an interim mitigation.
- 3. If available, disable the web application's ability to process executable file types in upload directories.
- 4. Contact Avaya support or visit the Avaya download portal (download.avaya.com) to obtain the security update addressing this vulnerability.
- 5. Apply the vendor-supplied patch or upgrade to the fixed release version.
- 6. Verify the fix by testing file upload functionality with non-executable files and confirming the vulnerability is resolved.
- 7. Monitor for any indicators of compromise and review access logs for suspicious file upload attempts.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3722 — 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-3722 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