CVE-2007-6050 Misconfiguration in n/a
High 7.2
Published
Updated
Check this codebase for CVE-2007-6050 and fix it if it is affected.
What it is: CVE-2007-6050 is a high-severity vulnerability in Ibm Db2 Universal Database, published on 20 Nov 2007.
Exploitation: There is no known exploitation of CVE-2007-6050 in the wild and no public exploit code.
Affected product: Ibm Db2 Universal Database. 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-2007-6050/ (Markdown: https://insights.sbomify.com/CVE-2007-6050/index.md)
An unspecified vulnerability in IBM DB2 involves the creation of an insecure directory, potentially allowing unauthorized access or privilege escalation.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2007-6050?
CVE-2007-6050 is a high-severity vulnerability in Ibm Db2 Universal Database, published on 20 Nov 2007.
Official description
Unspecified vulnerability in DB2LICD in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors, related to creation of an "insecure directory."
Weakness: CWE-264
Which versions are affected by CVE-2007-6050?
It affects 1 product.
Products include Ibm Db2 Universal Database.
How do I fix CVE-2007-6050?
No fix has been published for CVE-2007-6050 yet. Limit exposure of the affected software until one is available.
Is CVE-2007-6050 being exploited?
There is no known exploitation of CVE-2007-6050 in the wild and no public exploit code.
Other vulnerabilities in Ibm Db2 Universal Database
- CVE-2007-6045 Unspecified vulnerability in (1) DB2WATCH and (2) DB2FREEZE in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors.
- CVE-2007-6047 Command injection in n/a
- CVE-2007-6048 Misconfiguration in n/a
- CVE-2007-6051 IBM DB2 UDB 9.1 before Fixpak 4 assigns incorrect privileges to the (1) DB2ADMNS and (2) DB2USERS alternative groups, which has unknown impact.
- CVE-2005-4865 Memory corruption in n/a
Sources
Also known as GHSA-7cvr-982q-p89c.