# CVE-2021-40067: Missing authorization in NetMotion Mobility

> Attackers with valid credentials can bypass access controls to read and write data in the Mobility API if it is manually enabled.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vfw5-ghx2-pfhf

## What is CVE-2021-40067?

CVE-2021-40067 is a medium-severity missing authorization vulnerability in NetMotion Mobility, published on 16 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2021-40067?

It affects 1 product.


Products: Netmotionsoftware Mobility.

## How do I fix CVE-2021-40067?

No fix has been published for CVE-2021-40067 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-40067 being exploited?

There is no known exploitation of CVE-2021-40067 in the wild and no public exploit code.

## Other vulnerabilities in NetMotion Mobility

- [CVE-2021-40066](https://insights.sbomify.com/CVE-2021-40066/): Missing authorization in NetMotion Mobility (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-40067 and fix it if it is affected.

What it is: CVE-2021-40067 is a medium-severity missing authorization vulnerability in NetMotion Mobility, published on 16 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-40067 in the wild and no public exploit code.

Affected product: NetMotion Mobility. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-40067/ (Markdown: https://insights.sbomify.com/CVE-2021-40067/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-40067
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-40067
- OSV: https://osv.dev/vulnerability/CVE-2021-40067

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-40067/
Summaries are generated and may contain mistakes; the official description above is the record.