CVE-2004-1933 Information disclosure in n/a
Low 2.1
Published
Updated
Check this codebase for CVE-2004-1933 and fix it if it is affected.
What it is: CVE-2004-1933 is a low-severity vulnerability in n/a, published on 10 May 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-2004-1933 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-1933/ (Markdown: https://insights.sbomify.com/CVE-2004-1933/index.md)
Local attackers can read unauthorized messages due to world-readable database permissions in Citadel/UX.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2004-1933?
CVE-2004-1933 is a low-severity vulnerability in n/a, published on 10 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Citadel/UX 5.00 through 6.14 installs the database directory and files with world-read permissions, which could allow local users to bypass access controls and read unauthorized messages.
Which versions are affected by CVE-2004-1933?
How do I fix CVE-2004-1933?
No fix has been published for CVE-2004-1933 yet. Limit exposure of the affected software until one is available.
Is CVE-2004-1933 being exploited?
There is no known exploitation of CVE-2004-1933 in the wild and no public exploit code.
Sources
Also known as GHSA-r7hm-54xg-v8p6.