# CVE-2022-1300: Missing authentication in TRUMPF products may result in corruption of data

> Unauthenticated attackers can modify data or disrupt services in TRUMPF TruTops products due to missing authentication on exposed functions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-p7x3-m8gr-5hqm

## What is CVE-2022-1300?

CVE-2022-1300 is a critical missing authorization vulnerability in TRUMPF TruTops Boost, published on 2 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple Version of TRUMPF TruTops products expose a service function without necessary authentication. Execution of this function may result in unauthorized access to change of data or disruption of the whole service.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2022-1300?

It affects 3 products.


Products: Trumpf Trutops Boost, Trumpf Trutops Fab, Trumpf Trutops Monitor.

## How do I fix CVE-2022-1300?

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

## Is CVE-2022-1300 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1300 and fix it if it is affected.

What it is: CVE-2022-1300 is a critical missing authorization vulnerability in TRUMPF TruTops Boost, published on 2 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1300 in the wild and no public exploit code.

Affected product: TRUMPF TruTops Boost. 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-2022-1300/ (Markdown: https://insights.sbomify.com/CVE-2022-1300/index.md)
```

## Sources

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

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