# CVE-2024-6176: Port scanning vulnerability in LG SuperSign CMS

> An attacker can perform port scanning on LG SuperSign CMS due to lack of resource throttling, potentially revealing network topology information.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-7p4j-jw3c-v3x8

## What is CVE-2024-6176?

CVE-2024-6176 is a medium-severity vulnerability in LG SuperSign CMS, published on 20 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Allocation of Resources Without Limits or Throttling vulnerability in LG Electronics LG SuperSign CMS allows Port Scanning.This issue affects LG SuperSign CMS: from 4.1.3 before < 4.3.1.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2024-6176 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6176 is a medium-severity vulnerability in LG SuperSign CMS, published on 20 Jun 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-6176 in the wild and no public exploit code.

Affected product: LG SuperSign CMS. 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-6176/ (Markdown: https://insights.sbomify.com/CVE-2024-6176/index.md)
```

## Sources

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

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