CVE-2008-4809 Multiple unspecified vulnerabilities in the Profiles search pages in IBM Lotus Connections 2.x before 2.0.1 have unknown impact and attack v
Critical 10.0
Published
Updated
Check this codebase for CVE-2008-4809 and fix it if it is affected.
What it is: CVE-2008-4809 is a critical vulnerability in n/a, published on 31 Oct 2008.
Exploitation: There is no known exploitation of CVE-2008-4809 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-2008-4809/ (Markdown: https://insights.sbomify.com/CVE-2008-4809/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2008-4809?
CVE-2008-4809 is a critical vulnerability in n/a, published on 31 Oct 2008.
Official description
Multiple unspecified vulnerabilities in the Profiles search pages in IBM Lotus Connections 2.x before 2.0.1 have unknown impact and attack vectors related to "Active" content. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
Which versions are affected by CVE-2008-4809?
It affects 1 product.
Products include Ibm Lotus Connections.
How do I fix CVE-2008-4809?
No fix has been published for CVE-2008-4809 yet. Limit exposure of the affected software until one is available.
Is CVE-2008-4809 being exploited?
There is no known exploitation of CVE-2008-4809 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-85rg-hv4c-5cwf.