dbcve.org
Maarch RmApplication · Maarch

CVE-2022-37774

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-23
Fix available
A fix is available. Upgrade to 2.8.6 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
There is a broken access control vulnerability in the Maarch RM 2.8.3 solution. When accessing some specific document (pdf, email) from an archive, a preview is proposed by the application. This preview generates a URL including an md5 hash of the file accessed. The document's URL (https://{url}/tmp/{MD5 hash of the document}) is then accessible without authentication.

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 confidence

Maarch RM 2.8.3 generates preview URLs containing MD5 hashes of archived documents (PDFs, emails) stored at /tmp/{MD5}. These document URLs are accessible without any authentication, allowing unauthenticated users to view sensitive archived documents via direct URL access.

MitigationImplement proper authentication and session validation on the /tmp/ endpoint and document preview functionality, ensuring only authorized users with valid archive access permissions can retrieve documents.

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
Maarch RmApplication
Affected:>= 2.8, < 2.8.6= 2.9

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Maarch RM version
    Check your installed Maarch RM version by accessing the admin interface, checking the about page, or examining version files in the application root directory. Compare against affected versions: >= 2.8 and < 2.8.6, or exactly version 2.9.
    Affected if Version is 2.8.x (where x is 0-5) or exactly 2.9
  2. Verify /tmp endpoint accessibility
    Attempt to access a URL pattern like http://[host]/tmp/ directly from an unauthenticated browser or via curl without providing any session cookies or credentials.
    Affected if The /tmp/ directory or files within it are accessible without authentication (HTTP 200 response rather than 401/403)
  3. Check document preview URL format
    Generate a document preview within Maarch RM (as an authenticated user) and examine the URL generated. Look for URLs containing /tmp/ followed by a 32-character MD5 hash string.
    Affected if Preview URLs contain /tmp/{32-character-MD5-hash} pattern and are accessible without authentication
  4. Test unauthenticated document access
    Take a known document preview URL from step 3 and attempt to access it in a fresh browser session or with curl -i without any authentication headers.
    Affected if The document preview URL returns the actual file content without requiring login or session validation

You are affected if your Maarch RM version is >= 2.8 and < 2.8.6 or exactly 2.9, AND the /tmp/ endpoint with MD5-hashed document URLs is accessible without any authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.8.6 or later
Fixed in 2.8.6
Interim mitigation

Implement proper authentication and session validation on the /tmp/ endpoint and document preview functionality, ensuring only authorized users with valid archive access permissions can retrieve documents.

Recommended fix Moderate confidence

2.8.6 or later

  1. 1. Backup the current Maarch Rm installation and database before proceeding with the upgrade.
  2. 2. Download Maarch Rm version 2.8.6 or later from the official source (github.com/Maarch/maarchRM).
  3. 3. Review the release notes for version 2.8.6 to understand any specific upgrade procedures.
  4. 4. Deploy the new version by replacing the application files, following standard upgrade procedures.
  5. 5. Run any database migration scripts included in the 2.8.6 release.
  6. 6. Verify the fix by attempting to access document previews without authentication and confirm they are now properly protected.
  7. 7. Test normal authentication workflows to ensure the fix does not break legitimate access to documents.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maarch Rm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-37774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-37774 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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