CVE-2004-1509 Information disclosure in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2004-1509 and fix it if it is affected.
What it is: CVE-2004-1509 is a medium-severity vulnerability in n/a, published on 19 Feb 2005. 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-2004-1509 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-2004-1509/ (Markdown: https://insights.sbomify.com/CVE-2004-1509/index.md)
Remote attackers can obtain sensitive file path information via an invalid login parameter in WebCalendar, potentially aiding further attacks.
- 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-2004-1509?
CVE-2004-1509 is a medium-severity vulnerability in n/a, published on 19 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
validate.php in WebCalendar allows remote attackers to gain sensitive information via an invalid encoded_login parameter, which reveals the full path in an error message.
Which versions are affected by CVE-2004-1509?
How do I fix CVE-2004-1509?
No fix has been published for CVE-2004-1509 yet. Limit exposure of the affected software until one is available.
Is CVE-2004-1509 being exploited?
There is no known exploitation of CVE-2004-1509 in the wild and no public exploit code.
Sources
Also known as GHSA-pv77-qjw9-f43j.