CVE-2020-24573 BAB TECHNOLOGIE GmbH eibPort V3 prior to 3.8.3 devices allow denial of service (Uncontrolled Resource Consumption) via requests to the lighttpd component.
High 7.5
Published
Updated
Check this codebase for CVE-2020-24573 and fix it if it is affected.
What it is: CVE-2020-24573 is a high-severity vulnerability in n/a, published on 12 Nov 2020.
Exploitation: There is no known exploitation of CVE-2020-24573 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-2020-24573/ (Markdown: https://insights.sbomify.com/CVE-2020-24573/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2020-24573?
CVE-2020-24573 is a high-severity vulnerability in n/a, published on 12 Nov 2020.
Official description
BAB TECHNOLOGIE GmbH eibPort V3 prior to 3.8.3 devices allow denial of service (Uncontrolled Resource Consumption) via requests to the lighttpd component.
Weakness: CWE-400
Which versions are affected by CVE-2020-24573?
It affects 1 product.
Products include Bab-Technologie Eibport Firmware.
How do I fix CVE-2020-24573?
No fix has been published for CVE-2020-24573 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-24573 being exploited?
There is no known exploitation of CVE-2020-24573 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-f659-jgfp-vcm8.