CVE-2009-3399 Other in n/a
Medium 4.3
Published
Updated
Check this codebase for CVE-2009-3399 and fix it if it is affected.
What it is: CVE-2009-3399 is a medium-severity vulnerability in n/a, published on 22 Oct 2009. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2009-3399 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-2009-3399/ (Markdown: https://insights.sbomify.com/CVE-2009-3399/index.md)
Remote attackers can compromise the integrity of the WebLogic Server console, requiring immediate patching by administrators.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2009-3399?
CVE-2009-3399 is a medium-severity vulnerability in n/a, published on 22 Oct 2009. It can be exploited over the network.
Official description
Unspecified vulnerability in the WebLogic Server component in BEA Product Suite 7.0.6 and 8.1.5 allows remote attackers to affect integrity, related to WLS Console.
Which versions are affected by CVE-2009-3399?
It affects 1 product.
Products include Oracle Bea Product Suite.
How do I fix CVE-2009-3399?
No fix has been published for CVE-2009-3399 yet. Limit exposure of the affected software until one is available.
Is CVE-2009-3399 being exploited?
There is no known exploitation of CVE-2009-3399 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-x7vj-6hfr-gqfh.