CVE-2015-1445 Other in n/a
High 7.2
Published
Updated
Check this codebase for CVE-2015-1445 and fix it if it is affected.
What it is: CVE-2015-1445 is a high-severity vulnerability in n/a, published on 28 Aug 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1445 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-1445/ (Markdown: https://insights.sbomify.com/CVE-2015-1445/index.md)
Attackers can inject HTTP headers in the httpd package of fli4l, potentially manipulating responses or bypassing security controls.
- 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-2015-1445?
CVE-2015-1445 is a high-severity vulnerability in n/a, published on 28 Aug 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
HTTP header injection in the httpd package in fli4l before 3.10.1 and 4.0 before 2015-01-30.
Weakness: CWE-113
Which versions are affected by CVE-2015-1445?
It affects 1 product.
Products include Fli4l Fli4l.
How do I fix CVE-2015-1445?
No fix has been published for CVE-2015-1445 yet. Limit exposure of the affected software until one is available.
Is CVE-2015-1445 being exploited?
There is no known exploitation of CVE-2015-1445 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-8mj6-8866-c4f4.