CVE-2002-1711 Information disclosure in n/a
Low 2.1
Published
Updated
Check this codebase for CVE-2002-1711 and fix it if it is affected.
What it is: CVE-2002-1711 is a low-severity vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1711 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-2002-1711/ (Markdown: https://insights.sbomify.com/CVE-2002-1711/index.md)
Local users can read other users' attachments due to world-readable permissions on the temporary directory.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2002-1711?
CVE-2002-1711 is a low-severity vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
BasiliX 1.1.0 saves attachments in a world readable /tmp/BasiliX directory, which allows local users to read other users' attachments.
Which versions are affected by CVE-2002-1711?
It affects 1 product.
Products include Basilix Basilix Webmail.
How do I fix CVE-2002-1711?
No fix has been published for CVE-2002-1711 yet. Limit exposure of the affected software until one is available.
Is CVE-2002-1711 being exploited?
There is no known exploitation of CVE-2002-1711 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-3w9v-g7vm-2m73.