dbcve.org
MobilityApplication · Netmotionsoftware

CVE-2021-40067

MEDIUM · 6.8 CVSS v3.1 Published 2021-09-16
Fix available
A fix is available. Upgrade to 12.14 or later.
See remediation →
74/100
Remediation priority · Elevated
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
The access controls on the Mobility read-write API improperly validate user access permissions; this API is disabled by default. If the API is manually enabled, attackers with both network access to the API and valid credentials can read and write data to it; regardless of access control group membership settings. This vulnerability is fixed in Mobility v12.14.

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

The Mobility read-write API has improper access control validation that allows authenticated users to bypass group membership settings. When the API is manually enabled, attackers with valid credentials can read and write data regardless of configured access control groups, due to the validation failure.

MitigationUpgrade Mobility to v12.14 where the access control validation is fixed. Additionally, ensure the read-write API is only enabled if explicitly required and review access logs for any unauthorized data access while vulnerable.

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
MobilityApplication
Affected:< 12.14

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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. Verify if the Mobility read-write API is enabled
    Check the Mobility server configuration or admin console for the read-write API setting. Look for API enable/disable toggles or configuration files that control API access.
    Affected if The read-write API is manually enabled - this is the required condition for the vulnerability to be exploitable
  2. Determine the installed Netmotionsoftware Mobility version
    Use the Mobility server's version information command, check the About section in the admin console, or examine version metadata in the installation directory.
    Affected if The installed version is any version below 12.14 (e.g., 12.13, 12.12, earlier versions)
  3. Review access control group configurations for the API
    Examine the access control settings that govern which users can access the read-write API, specifically check group membership enforcement rules.
    Affected if Users assigned to restricted groups can access data outside their group permissions when using the API

You are affected if the read-write API is enabled AND your Mobility version is below 12.14, allowing authenticated users to bypass group-based access restrictions.

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 12.14 or later
Fixed in 12.14
Interim mitigation

Upgrade Mobility to v12.14 where the access control validation is fixed. Additionally, ensure the read-write API is only enabled if explicitly required and review access logs for any unauthorized data access while vulnerable.

Recommended fix High confidence

Mobility v12.14

  1. 1. Back up the current NetMotion Mobility configuration and database
  2. 2. Obtain NetMotion Mobility version 12.14 or later from the official vendor download site
  3. 3. Follow the vendor's documented upgrade procedure to upgrade the Mobility installation to v12.14
  4. 4. After upgrade, verify the read-write API access controls now properly enforce user permissions based on access control group membership
  5. 5. Confirm the upgrade was successful by checking the Mobility version information

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

Fix this in Mobility Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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