dbcve.org
Marval MsmApplication · Marvalglobal

CVE-2022-31883

HIGH · 8.8 CVSS v3.1 Published 2022-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
Marval MSM v14.19.0.12476 is has an Insecure Direct Object Reference (IDOR) vulnerability. A low privilege user is able to see other users API Keys including the Admins API Keys.

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

Marval MSM v14.19.0.12476 contains an Insecure Direct Object Reference (IDOR) vulnerability where the application fails to properly validate user authorization when accessing API key resources. Low-privileged users can access other users' API keys, including administrator API keys, by manipulating object references in API requests.

MitigationImplement proper authorization checks to verify the requesting user has permission to access the specific API key being requested, enforce access control validation on all sensitive endpoints, and rotate any exposed administrative API keys as a precaution.

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
Marval MsmApplication
Affected:= 14.19.0.12476

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify Marval MSM installation
    Locate the Marval MSM application on your system. This is typically a web-based application. Check your installed programs list, application directory, or consult your system administrator to confirm Marval MSM is deployed.
    Affected if Marval MSM is not installed on your environment - you are not affected.
  2. Check the installed version
    Access the application's about page, help menu, or admin panel to find the version number. Alternatively, check the installation directory for version files or contact your Marval MSM administrator for the version information.
    Affected if The version is exactly 14.19.0.12476 - proceed to next check. If version differs, you are likely not affected by this specific CVE.
  3. Confirm API key functionality is enabled
    Check if the API functionality module is enabled in the application. This is typically found in the admin settings under API integrations, API keys, or developer settings. Look for options related to API key management.
    Affected if API key functionality is disabled or not configured - the vulnerability cannot be exploited.
  4. Test for IDOR on API key endpoints
    Using a low-privileged user account, attempt to access API key resources by manipulating object references in API requests. For example, try to access /api/keys/{id} or similar endpoints, changing the {id} parameter to reference other users' API key identifiers. Use browser dev tools or API testing tools to observe if other users' keys are returned.
    Affected if Low-privileged users can view, modify, or delete API keys belonging to other users, including admin API keys - you are affected by this IDOR vulnerability.

You are affected if Marval MSM version 14.19.0.12476 is installed with API key functionality enabled, and low-privileged users can access or manipulate other users' API keys through the API endpoints.

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

Implement proper authorization checks to verify the requesting user has permission to access the specific API key being requested, enforce access control validation on all sensitive endpoints, and rotate any exposed administrative API keys as a precaution.

Fix this in Marval Msm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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