CVE-2006-6069 Information disclosure in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2006-6069 and fix it if it is affected.
What it is: CVE-2006-6069 is a medium-severity vulnerability in n/a, published on 22 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6069 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-6069/ (Markdown: https://insights.sbomify.com/CVE-2006-6069/index.md)
Remote attackers can obtain the installation path via an invalid gal parameter in mAlbum, exposing sensitive server information.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2006-6069?
CVE-2006-6069 is a medium-severity vulnerability in n/a, published on 22 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
index.php in mAlbum 0.3 and earlier allows remote attackers to obtain the installation path via an invalid gal parameter.
Which versions are affected by CVE-2006-6069?
It affects 1 product.
Products include Malbum Malbum.
How do I fix CVE-2006-6069?
No fix has been published for CVE-2006-6069 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-6069 being exploited?
There is no known exploitation of CVE-2006-6069 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-mjwp-56xv-r5f3.