CVE-2006-4461 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2006-4461 and fix it if it is affected.
What it is: CVE-2006-4461 is a critical vulnerability in n/a, published on 31 Aug 2006.
Exploitation: There is no known exploitation of CVE-2006-4461 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-2006-4461/ (Markdown: https://insights.sbomify.com/CVE-2006-4461/index.md)
Paessler IPCheck Server Monitor fails to properly validate acceptable host IP addresses in probe settings, with unknown impact.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2006-4461?
CVE-2006-4461 is a critical vulnerability in n/a, published on 31 Aug 2006.
Official description
Paessler IPCheck Server Monitor before 5.3.3.639/640 does not properly implement a "list of acceptable host IP addresses in the probe settings," which has unknown impact and attack vectors.
Which versions are affected by CVE-2006-4461?
It affects 1 product.
Products include Paessler Ipcheck Server Monitor.
How do I fix CVE-2006-4461?
No fix has been published for CVE-2006-4461 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-4461 being exploited?
There is no known exploitation of CVE-2006-4461 in the wild and no public exploit code.
Sources
Also known as GHSA-3368-v7m5-7xg6.