dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-5202

HIGH · 7.7 CVSS v3.1 Published 2024-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
Arbitrary File Read in OpenText Dimensions RM allows authenticated users to read files stored on the server via webservices

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

OpenText Dimensions RM contains an arbitrary file read vulnerability in its webservices component. Authenticated users can exploit this to read arbitrary files on the server file system by manipulating file path parameters in webservice requests. This could lead to exposure of sensitive configuration files, credentials, or other confidential data.

MitigationApply the vendor-supplied patch for CVE-2024-5202 from OpenText. Review and restrict webservice permissions to limit which authenticated users can access file-related operations, and monitor for suspicious file access patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Identify OpenText Dimensions RM installation
    Search for Dimensions RM installation directories or check installed programs on the server. Common locations may include C:\Program Files\OpenText\ or /opt/opentext/ on Linux systems. Look for executable files like dmbasic.exe, rmweb.exe, or service processes named 'Dimensions RM'
    Affected if OpenText Dimensions RM software is found installed on the system
  2. Determine installed Dimensions RM version
    Check the installed version by reviewing installation logs, the product GUI about section, or registry entries on Windows. The version is typically displayed in the Dimensions RM admin console or can be retrieved via command line tools provided with the installation
    Affected if The installed version matches or predates any version prior to the vendor patch release date for CVE-2024-5202
  3. Verify webservices component is enabled
    Check Dimensions RM configuration files (such as web.config or rmwebsrv.cfg) for webservice endpoint configurations. Access the Dimensions RM administration interface and navigate to System Configuration or Web Services settings to confirm webservices are active
    Affected if Webservices component is enabled and accessible via HTTP/HTTPS endpoints
  4. Review webservice user permissions
    Examine Dimensions RM user roles and permissions through the admin console. Check which users or groups have access to document management, file operations, or webservice API functions. Focus on permissions related to file retrieval or document import features
    Affected if Any authenticated users have permissions to perform file-related operations through the webservices API
  5. Inspect webservice logs for suspicious file access
    Review Dimensions RM webservice logs (typically found in the logs or tomcat/logs subdirectory of the installation) for anomalous requests. Look for patterns such as requests containing directory traversal sequences (../) or access to system configuration files outside normal document repositories
    Affected if Log entries show unusual file path parameters in webservice requests, especially attempts to access system files outside the document storage area

A user is affected if OpenText Dimensions RM is installed with webservices enabled and any authenticated users have access to file-related webservice operations, particularly if the installed version predates the CVE-2024-5202 patch.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch for CVE-2024-5202 from OpenText. Review and restrict webservice permissions to limit which authenticated users can access file-related operations, and monitor for suspicious file access patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5202 — 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-2024-5202 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