CVE-2022-46404
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 command injection vulnerability has been identified in Atos Unify OpenScape 4000 Assistant and Unify OpenScape 4000 Manager (8 before R2.22.18, 10 before 0.28.13, and 10 R1 before R1.34.4) that may allow an unauthenticated attacker to upload arbitrary files and achieve administrative access to the system.
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 confidenceA command injection vulnerability in Atos Unify OpenScape 4000 allows unauthenticated attackers to upload arbitrary files to the system and escalate privileges to administrative access. The flaw affects multiple version branches (8, 10, and 10 R1) prior to the specified patched releases.
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= 10= 8= 10CVSS 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 the installed OpenScape 4000 product and versionAccess the web administration interface and navigate to the system information or about section to retrieve the exact version number (such as 8.x, 10.x, or 10 R1.x). Alternatively, check the system using the CLI command provided by the vendor documentation for your deployment.Affected if The version is 8.x prior to R2.22.18, 10.x prior to 0.28.13, or 10 R1.x prior to R1.34.4.
-
Confirm the web management interface is accessibleVerify that the OpenScape 4000 web interface (typically on ports 80/443 or vendor-specified ports) is reachable from network locations. Check firewall rules and service status.Affected if The web interface is exposed and the installed version falls within the affected ranges.
-
Review web server logs for suspicious upload requestsExamine the web server logs (usually in /var/log or vendor-specific log directories) for POST requests to upload endpoints that contain unusual parameters, unexpected file extensions, or shell metacharacters commonly used in command injection attempts.Affected if Log entries show unauthorized file upload attempts or command injection patterns targeting the upload functionality.
-
Check for unexpected administrative accountsReview the user management section of the OpenScape 4000 Manager or Assistant interface for newly created accounts with administrative privileges that were not provisioned through official channels.Affected if Unknown administrative accounts exist, indicating possible privilege escalation via this vulnerability.
You are affected if the installed OpenScape 4000 version is 8.x before R2.22.18, 10.x before 0.28.13, or 10 R1.x before R1.34.4, and the web management interface is accessible.
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 · scopedApply the vendor-supplied patches to upgrade to version R2.22.18 (branch 8), 0.28.13 (branch 10), or R1.34.4 (branch 10 R1) as appropriate for the deployed version.
R2.22.18 (v8), 0.28.13 (v10), or R1.34.4 (v10 R1) depending on installed version branch
- Identify the currently installed version of Unify Openscape 4000 Assistant or Manager
- Determine which version branch is in use (v8, v10, or v10 R1)
- For version 8: Upgrade to version R2.22.18 or later
- For version 10: Upgrade to version 0.28.13 or later
- For version 10 R1: Upgrade to version R1.34.4 or later
- Obtain the upgrade package from the official Unify support portal (networks.unify.com)
- Follow the standard Unify upgrade procedure for the specific version
- After upgrade, verify the system is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46404 — 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-46404 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