# CVE-2021-38137: Missing authorization in n/a

> Corero SecureWatch fails to enforce role-based access controls, allowing users to perform unauthorized actions beyond their assigned privileges.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/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:** 6 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-93wr-f53h-25wp

## What is CVE-2021-38137?

CVE-2021-38137 is a high-severity missing authorization vulnerability in n/a, published on 6 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Corero SecureWatch Managed Services 9.7.2.0020 does not correctly check swa-monitor and cns-monitor user’s privileges, allowing a user to perform actions not belonging to his role.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Corero Securewatch Managed Services.

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

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

## Is CVE-2021-38137 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38136](https://insights.sbomify.com/CVE-2021-38136/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-38137 is a high-severity missing authorization vulnerability in n/a, published on 6 Aug 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-38137 in the wild and no public exploit code.

Affected product: n/a. 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-38137/ (Markdown: https://insights.sbomify.com/CVE-2021-38137/index.md)
```

## Sources

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

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