CVE-2006-6967 DO NOT USE THIS CANDIDATE NUMBER.
Not scored
Published
Updated
Check this codebase for CVE-2006-6967 and fix it if it is affected.
What it is: CVE-2006-6967 is a vulnerability, published on 4 Feb 2007.
Exploitation: There is no known exploitation of CVE-2006-6967 in the wild and no public exploit code.
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-2006-6967/ (Markdown: https://insights.sbomify.com/CVE-2006-6967/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2006-6967?
CVE-2006-6967 is a vulnerability, published on 4 Feb 2007.
Official description
DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: None. Reason: this candidate is solely about a configuration that does not directly introduce security vulnerabilities, so it is more appropriate to cover under the Common Configuration Enumeration (CCE). In addition, it describes standard behavior (publication of revocation lists) and as such does not cross privilege boundaries. Notes: the former description is: "Check Point FireWall-1 allows remote attackers to obtain certificate revocation lists (CRLs) and other unspecified sensitive information via an HTTP request for the top-level URI on the internal certificate authority (ICA) port (18264/tcp).
Which versions are affected by CVE-2006-6967?
How do I fix CVE-2006-6967?
No fix has been published for CVE-2006-6967 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-6967 being exploited?
There is no known exploitation of CVE-2006-6967 in the wild and no public exploit code.