CVE-2003-1138 The default configuration of Apache 2.0.40, as shipped with Red Hat Linux 9.0, allows remote attackers to list directory contents, even if a
Medium 5.0
Published
Updated
Check this codebase for CVE-2003-1138 and fix it if it is affected.
What it is: CVE-2003-1138 is a medium-severity vulnerability in n/a, published on 10 May 2005.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1138 exists.
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-2003-1138/ (Markdown: https://insights.sbomify.com/CVE-2003-1138/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2003-1138?
CVE-2003-1138 is a medium-severity vulnerability in n/a, published on 10 May 2005.
Official description
The default configuration of Apache 2.0.40, as shipped with Red Hat Linux 9.0, allows remote attackers to list directory contents, even if auto indexing is turned off and there is a default web page configured, via a GET request containing a double slash (//).
Which versions are affected by CVE-2003-1138?
It affects 1 product.
Products include Redhat Interchange.
How do I fix CVE-2003-1138?
No fix has been published for CVE-2003-1138 yet. Limit exposure of the affected software until one is available.
Is CVE-2003-1138 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1138 exists.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in n/a
Sources
Also known as GHSA-rpv4-252f-9j5c.