# CVE-2024-11075: SICK Incoming Goods Suite privilege escalation vulnerability

> An attacker with local access can escalate privileges to administrative level due to Docker containers running with root permissions in the SICK Incoming Goods Suite.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-j3h2-4rr5-87p6

## What is CVE-2024-11075?

CVE-2024-11075 is a high-severity vulnerability in SICK Incoming Goods Suite, published on 19 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Incoming Goods Suite allows a user with unprivileged access to the underlying system (e.g. local or via SSH) a privilege escalation to the administrative level due to the usage of component vendor Docker images running with root permissions. Exploiting this misconfiguration leads to the fact that an attacker can gain administrative control. over the whole system.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2024-11075?


## How do I fix CVE-2024-11075?

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

## Is CVE-2024-11075 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11075 and fix it if it is affected.

What it is: CVE-2024-11075 is a high-severity vulnerability in SICK Incoming Goods Suite, published on 19 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11075 in the wild and no public exploit code.

Affected product: SICK Incoming Goods Suite. 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-2024-11075/ (Markdown: https://insights.sbomify.com/CVE-2024-11075/index.md)
```

## Sources

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

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