dbcve.org
MobilityApplication · Netmotionsoftware

CVE-2021-40066

MEDIUM · 5.3 CVSS v3.1 Published 2021-09-16
Fix available
A fix is available. Upgrade to 11.76 / 12.14 or later.
See remediation →
59/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-only API improperly validate user access permissions. Attackers with both network access to the API and valid credentials can read data from it; regardless of access control group membership settings. This vulnerability is fixed in Mobility v11.76 and 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

This is an access control bypass vulnerability in the Mobility read-only API where the system improperly validates user permissions. Authenticated users with network access can read data beyond their intended access level, bypassing access control group membership restrictions.

MitigationApply the vendor patch by updating Mobility to version 11.76 or 12.14 (or later), then verify that access controls now properly enforce group-based restrictions on API data access.

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:< 11.76>= 12.00, < 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
None
Availability
None

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

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

  1. Identify Mobility version
    Locate the installed Netmotionsoftware Mobility version number through the product's about page, system information, or version lookup command provided by the software
    Affected if The installed version is less than 11.76, or is between 12.00 and 12.13 inclusive
  2. Confirm read-only API is active
    Determine whether the Mobility read-only API feature or module is enabled on the system through the admin console, configuration settings, or running services list
    Affected if The read-only API is enabled and running
  3. Review API access control configuration
    Inspect the access control group membership settings for the read-only API to see which users or groups are permitted to access API endpoints
    Affected if Users with limited group permissions can access data outside their assigned group scope through the API
  4. Test cross-group data access
    If you have access to multiple user accounts with different access control group memberships, use the read-only API to query data belonging to groups you are not a member of
    Affected if An authenticated user can successfully retrieve data from groups they are not assigned to, indicating the access control bypass is present
  5. Compare against vendor version reference
    Cross-reference your identified version against the fixed releases (11.76 and 12.14) documented in the CVE advisory
    Affected if The installed version predates the patched releases and the read-only API is in use

You are affected if your Netmotionsoftware Mobility version is below 11.76 or between 12.00 and 12.13, and the read-only API is enabled, allowing authenticated users to access data outside their access control group 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 11.76 / 12.14 or later
Fixed in 11.7612.14
Interim mitigation

Apply the vendor patch by updating Mobility to version 11.76 or 12.14 (or later), then verify that access controls now properly enforce group-based restrictions on API data access.

Recommended fix High confidence

Mobility v11.76 (if on v10.x/11.x) or Mobility v12.14 (if on v12.x)

  1. 1. Back up the current NetMotion Mobility configuration and database
  2. 2. Verify current installed version using the Mobility administrative console or CLI
  3. 3. Download the appropriate Mobility upgrade package (v11.76 or v12.14) from the official NetMotion software portal at www.netmotionsoftware.com
  4. 4. Review the upgrade guide specific to your current version for pre-upgrade requirements
  5. 5. Apply the upgrade following the standard Mobility upgrade procedure
  6. 6. After upgrade, verify the access control group settings are properly enforced in the Mobility read-only API
  7. 7. Test that users outside their assigned access control groups cannot read unauthorized data
Caveat Review NetMotion release notes for v11.76 and v12.14 for any configuration changes or migration requirements before upgrading

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

Fix this in Mobility Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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