# CVE-2021-32503: Missing authorization in SICK FTMg

> Unauthenticated attackers can access restricted maintenance URLs on SICK FTMg devices, exposing sensitive information for further attacks.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mg2c-c9jj-4xgv

## What is CVE-2021-32503?

CVE-2021-32503 is a medium-severity missing authorization vulnerability in SICK FTMg, published on 1 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unauthenticated users can access sensitive web URLs through GET request, which should be restricted to maintenance users only. A malicious attacker could use this sensitive information’s to launch further attacks on the system.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Sick Ftmg Firmware.

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

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

## Is CVE-2021-32503 being exploited?

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

## Other vulnerabilities in SICK FTMg

- [CVE-2021-32504](https://insights.sbomify.com/CVE-2021-32504/): Missing authorization in SICK FTMg (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-32503 is a medium-severity missing authorization vulnerability in SICK FTMg, published on 1 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32503 in the wild and no public exploit code.

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

## Sources

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

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