CVE-2019-25219 Other in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2019-25219 and fix it if it is affected.
What it is: CVE-2019-25219 is a high-severity vulnerability in n/a, published on 29 Oct 2024. 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-2019-25219 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-2019-25219/ (Markdown: https://insights.sbomify.com/CVE-2019-25219/index.md)
The Asio C++ library fails to handle specific SSL errors, potentially leading to application crashes or denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-25219?
CVE-2019-25219 is a high-severity vulnerability in n/a, published on 29 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Asio C++ Library before 1.13.0 lacks a fallback error code in the case of SSL_ERROR_SYSCALL with no associated error information from the SSL library being used.
Weakness: CWE-1188
Which versions are affected by CVE-2019-25219?
How do I fix CVE-2019-25219?
Upgrade to a fixed version.
Is CVE-2019-25219 being exploited?
There is no known exploitation of CVE-2019-25219 in the wild and no public exploit code.
Sources
Also known as AZL-52023, AZL-52029, DEBIAN-CVE-2019-25219, GHSA-cwg2-qmg3-3f6x, UBUNTU-CVE-2019-25219.