CVE-2022-35216
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 image 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 contains a path traversal vulnerability in its mail image relay function. An unauthenticated remote attacker can exploit this by manipulating file path parameters to bypass authentication and read arbitrary system files on the host server.
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.
-
Confirm Omicard Edm installationLocate the Omicard Edm application on the system and identify its installation directory. Look for executable files, web application roots, or service binaries associated with the Omicard Edm Project.Affected if Omicard Edm software is present on the system
-
Determine installed versionQuery the application for its version number. Check application metadata files, about dialogs, or version information exposed by the software itself. Compare the found version against the affected range of >= 5.8, <= 6.0.Affected if Installed version falls within 5.8 to 6.0 inclusive
-
Identify mail image relay function exposureLocate the mail image relay function within the application. Determine if this component is accessible via HTTP/HTTPS endpoints or other network interfaces. Review application routing configuration to find endpoints handling mail image requests.Affected if The mail image relay function is exposed and accessible to network requests
-
Check unauthenticated access configurationReview the application authentication configuration for the mail image relay endpoint. Determine whether unauthenticated or anonymous access is permitted to this function. Look for authentication enforcement settings in the application configuration.Affected if Unauthenticated access to the mail image relay function is permitted
-
Test path traversal vulnerabilitySend a crafted request to the mail image relay endpoint with path traversal sequences (such as ../../) in file path parameters. Observe if the application returns files from outside the intended directory or system files.Affected if The application returns arbitrary system files in response to path traversal patterns
A system is affected if Omicard Edm versions 5.8 through 6.0 are installed with the mail image relay function exposed and accessible to unauthenticated 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.
From vendor dataImplement strict input validation and canonicalization on all file path parameters in the mail image relay function, ensuring paths resolve within allowed directories and cannot traverse outside the intended scope. Additionally, enforce proper authentication checks before any file operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35216 — 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-35216 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