CVE-2020-15688 The HTTP Digest Authentication in the GoAhead web server before 5.1.2 does not completely protect against replay attacks.
High 8.8
Published
Updated
Check this codebase for CVE-2020-15688 and fix it if it is affected.
What it is: CVE-2020-15688 is a high-severity vulnerability in n/a, published on 23 Jul 2020.
Exploitation: There is no known exploitation of CVE-2020-15688 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-15688/ (Markdown: https://insights.sbomify.com/CVE-2020-15688/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2020-15688?
CVE-2020-15688 is a high-severity vulnerability in n/a, published on 23 Jul 2020.
Official description
The HTTP Digest Authentication in the GoAhead web server before 5.1.2 does not completely protect against replay attacks. This allows an unauthenticated remote attacker to bypass authentication via capture-replay if TLS is not used to protect the underlying communication channel.
Weakness: CWE-294
Which versions are affected by CVE-2020-15688?
It affects 1 product.
Products include Embedthis Goahead.
How do I fix CVE-2020-15688?
No fix has been published for CVE-2020-15688 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-15688 being exploited?
There is no known exploitation of CVE-2020-15688 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-6r2c-458p-644h.