CVE-2020-23249 Hardcoded credentials in n/a
Medium 4.7
Published
Updated
Check this codebase for CVE-2020-23249 and fix it if it is affected.
What it is: CVE-2020-23249 is a medium-severity vulnerability in n/a, published on 5 Jan 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-23249 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-23249/ (Markdown: https://insights.sbomify.com/CVE-2020-23249/index.md)
Attackers can access the Redis database using plaintext credentials stored in GigaVUE-OS, potentially leading to data exposure or unauthorized access.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-23249?
CVE-2020-23249 is a medium-severity vulnerability in n/a, published on 5 Jan 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
GigaVUE-OS (GVOS) 5.4 - 5.9 stores a Redis database password in plaintext.
Weakness: CWE-312
Which versions are affected by CVE-2020-23249?
It affects 1 product.
Products include Gigamon Gigavue-Os.
How do I fix CVE-2020-23249?
No fix has been published for CVE-2020-23249 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-23249 being exploited?
There is no known exploitation of CVE-2020-23249 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-75xc-p7x5-2rwx.