OSV-2018-369 Negative-size-param in get_urls_css
Not scored
Published
Check this codebase for OSV-2018-369 and fix it if it is affected.
What it is: OSV-2018-369 is a vulnerability in wget, published on 15 Jan 2021.
Exploitation: There is no known exploitation of OSV-2018-369 in the wild and no public exploit code.
Affected packages and fixed versions:
- wget (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2018-369/ (Markdown: https://insights.sbomify.com/OSV-2018-369/index.md)
A negative size parameter in get_urls_css can cause a crash, potentially leading to denial of service in applications using this library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2018-369?
OSV-2018-369 is a vulnerability in wget, published on 15 Jan 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8032
Crash type: Negative-size-param
Crash state:
get_urls_css
wget_css_fuzzer.c
Which versions are affected by OSV-2018-369?
1 open source package ship an affected version, including wget.
| Package | Affected | Fixed in |
|---|---|---|
wget OSS-Fuzz | All versions | None |
How do I fix OSV-2018-369?
No fix has been published for OSV-2018-369 yet. Limit exposure of the affected software until one is available.
Is OSV-2018-369 being exploited?
There is no known exploitation of OSV-2018-369 in the wild and no public exploit code.