CVE-2022-32963
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 · uneditedOMICARD EDM’s mail file relay function has a path traversal vulnerability. An unauthenticated remote attacker can exploit this vulnerability to by-pass authentication and access arbitrary system 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 · high confidenceOMICARD EDM's mail file relay function contains a path traversal vulnerability that allows unauthenticated remote attackers to bypass authentication and read arbitrary system files by manipulating file path inputs. This is a classic directory traversal issue where the application fails to properly sanitize file path parameters, enabling attackers to use '../' sequences to escape the intended directory and access sensitive system 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>= 5.8, <= 6.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 OMICARD EDM installationLocate the OMICARD EDM application on the system. Check for the presence of the web application files or service running on typical ports (commonly 80/443 for web apps). Use 'netstat -an | grep LISTEN' or check known installation directories if accessible.Affected if OMICARD EDM is installed and accessible on the network
-
Confirm installed versionAccess the application's admin panel, about page, or check version files in the installation directory. Common locations include a 'version', 'info', or 'about' endpoint, or a configuration file within the app directory. Compare the found version against the affected range: >= 5.8 AND <= 6.0Affected if The installed version falls within 5.8 to 6.0 inclusive
-
Identify mail file relay function exposureLocate the mail file relay functionality within the application. This is typically a feature for sending files via email. Check if this endpoint is exposed to the network without authentication. Common paths may include '/mail', '/file relay', '/send mail', or similar URL patterns in the application's routing structure.Affected if The mail file relay function is accessible via HTTP/HTTPS without requiring authentication
-
Test for path traversal vulnerabilityIf the mail file relay endpoint accepts a file path parameter, attempt a test request using path traversal sequences such as '../' or '..\' to access files outside the intended directory. For example, append '?file=../../../../etc/passwd' or similar to the relay endpoint URL. Observe if the application returns file contents from outside the expected directory.Affected if The application returns contents of files outside the intended mail attachment directory when using '../' sequences in the file path parameter
A system is affected if OMICARD EDM versions 5.8 through 6.0 are installed with the mail file relay function exposed and accessible without authentication, allowing path traversal characters to escape the intended directory.
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 dataImplement strict input validation on file path parameters using allowlists, canonicalize paths using realpath() or equivalent functions, and verify that resolved paths remain within the intended base directory before any file operations. Disable directory listing and ensure proper access controls are enforced.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32963 — 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-32963 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