CVE-2015-7919 SearchBlox 8.3 before 8.3.1 allows remote attackers to write to the config file, and consequently cause a denial of service (application cra
Critical 10.0
Published
Updated
Check this codebase for CVE-2015-7919 and fix it if it is affected.
What it is: CVE-2015-7919 is a critical vulnerability in n/a, published on 21 Dec 2015.
Exploitation: There is no known exploitation of CVE-2015-7919 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-2015-7919/ (Markdown: https://insights.sbomify.com/CVE-2015-7919/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2015-7919?
CVE-2015-7919 is a critical vulnerability in n/a, published on 21 Dec 2015.
Official description
SearchBlox 8.3 before 8.3.1 allows remote attackers to write to the config file, and consequently cause a denial of service (application crash), via unspecified vectors.
Weakness: CWE-264
Which versions are affected by CVE-2015-7919?
It affects 1 product.
Products include Searchblox Searchblox.
How do I fix CVE-2015-7919?
No fix has been published for CVE-2015-7919 yet. Limit exposure of the affected software until one is available.
Is CVE-2015-7919 being exploited?
There is no known exploitation of CVE-2015-7919 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-whx8-5pxp-fhhv.