RHSA-2002:217
Vulnerability from csaf_redhat - Published: 2002-11-08 11:16 - Updated: 2025-11-21 17:25The default servlet (org.apache.catalina.servlets.DefaultServlet) in Tomcat 4.0.4 and 4.1.10 and earlier allows remote attackers to read source code for server files via a direct request to the servlet.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Red Hat Stronghold 4
Red Hat / Stronghold Cross Platform
|
cpe:/a:redhat:stronghold:4
|
— |
Vendor Fix
fix
|
{
"document": {
"aggregate_severity": {
"namespace": "https://access.redhat.com/security/updates/classification/",
"text": "Important"
},
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Copyright \u00a9 Red Hat, Inc. All rights reserved.",
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "Updated tomcat packages are now available for Stronghold Cross Platform to\nclose a JSP source code exposure vulnerability.",
"title": "Topic"
},
{
"category": "general",
"text": "Tomcat is the servlet container that is used in the official Reference\nImplementation for the Java Servlet and JavaServer Pages technologies. A\nsource code exposure vulnerability has been found that affects Tomcat\nversions 4.0.0 through 4.0.4 and 4.1.0 through 4.1.10.\n\nUsing a carefully crafted request, a remote attacker can read the source\ncode of any deployed JSP file.\n\nStronghold Cross Platform shipped with Tomcat version 4.0.3 and is\ntherefore susceptible to this vulnerability.\n\nAll users are advised to upgrade to these errata packages containing\nTomcat version 4.0.5 which is not vulnerable to this issue.",
"title": "Details"
},
{
"category": "legal_disclaimer",
"text": "This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.",
"title": "Terms of Use"
}
],
"publisher": {
"category": "vendor",
"contact_details": "https://access.redhat.com/security/team/contact/",
"issuing_authority": "Red Hat Product Security is responsible for vulnerability handling across all Red Hat products and services.",
"name": "Red Hat Product Security",
"namespace": "https://www.redhat.com"
},
"references": [
{
"category": "self",
"summary": "https://access.redhat.com/errata/RHSA-2002:217",
"url": "https://access.redhat.com/errata/RHSA-2002:217"
},
{
"category": "external",
"summary": "https://access.redhat.com/security/updates/classification/#important",
"url": "https://access.redhat.com/security/updates/classification/#important"
},
{
"category": "external",
"summary": "http://marc.theaimsgroup.com/?l=bugtraq\u0026m=103288242014253\u0026w=2",
"url": "http://marc.theaimsgroup.com/?l=bugtraq\u0026m=103288242014253\u0026w=2"
},
{
"category": "external",
"summary": "71144",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=71144"
},
{
"category": "external",
"summary": "71167",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=71167"
},
{
"category": "external",
"summary": "71175",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=71175"
},
{
"category": "external",
"summary": "71177",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=71177"
},
{
"category": "external",
"summary": "73724",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=73724"
},
{
"category": "self",
"summary": "Canonical URL",
"url": "https://security.access.redhat.com/data/csaf/v2/advisories/2002/rhsa-2002_217.json"
}
],
"title": "Red Hat Security Advisory: tomcat security update for Stronghold",
"tracking": {
"current_release_date": "2025-11-21T17:25:08+00:00",
"generator": {
"date": "2025-11-21T17:25:08+00:00",
"engine": {
"name": "Red Hat SDEngine",
"version": "4.6.12"
}
},
"id": "RHSA-2002:217",
"initial_release_date": "2002-11-08T11:16:00+00:00",
"revision_history": [
{
"date": "2002-11-08T11:16:00+00:00",
"number": "1",
"summary": "Initial version"
},
{
"date": "2002-09-30T00:00:00+00:00",
"number": "2",
"summary": "Last updated version"
},
{
"date": "2025-11-21T17:25:08+00:00",
"number": "3",
"summary": "Last generated version"
}
],
"status": "final",
"version": "3"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_name",
"name": "Red Hat Stronghold 4",
"product": {
"name": "Red Hat Stronghold 4",
"product_id": "Red Hat Stronghold 4",
"product_identification_helper": {
"cpe": "cpe:/a:redhat:stronghold:4"
}
}
}
],
"category": "product_family",
"name": "Stronghold Cross Platform"
}
],
"category": "vendor",
"name": "Red Hat"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2002-1148",
"ids": [
{
"system_name": "Red Hat Bugzilla ID",
"text": "1616844"
}
],
"notes": [
{
"category": "description",
"text": "The default servlet (org.apache.catalina.servlets.DefaultServlet) in Tomcat 4.0.4 and 4.1.10 and earlier allows remote attackers to read source code for server files via a direct request to the servlet.",
"title": "Vulnerability description"
},
{
"category": "summary",
"text": "security flaw",
"title": "Vulnerability summary"
}
],
"product_status": {
"fixed": [
"Red Hat Stronghold 4"
]
},
"references": [
{
"category": "self",
"summary": "Canonical URL",
"url": "https://access.redhat.com/security/cve/CVE-2002-1148"
},
{
"category": "external",
"summary": "RHBZ#1616844",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1616844"
},
{
"category": "external",
"summary": "https://www.cve.org/CVERecord?id=CVE-2002-1148",
"url": "https://www.cve.org/CVERecord?id=CVE-2002-1148"
},
{
"category": "external",
"summary": "https://nvd.nist.gov/vuln/detail/CVE-2002-1148",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2002-1148"
}
],
"release_date": "2002-09-24T00:00:00+00:00",
"remediations": [
{
"category": "vendor_fix",
"date": "2002-11-08T11:16:00+00:00",
"details": "The updated packages are now available via the update agent service. Run\nthe command\n\n$ bin/agent\n\nfrom the Stronghold 4 install root to upgrade an existing Stronghold 4\ninstallation to the new package versions. After upgrading Stronghold, the\nserver must be completely restarted by running the following commands from\nthe install root:\n\n$ bin/stop-server\n$ bin/stop-tomcat\n$ bin/start-tomcat\n$ bin/start-server\n\nFor more information on how to upgrade between releases of Stronghold 4,\nsee http://stronghold.redhat.com/support/upgrade-sh4",
"product_ids": [
"Red Hat Stronghold 4"
],
"restart_required": {
"category": "none"
},
"url": "https://access.redhat.com/errata/RHSA-2002:217"
}
],
"threats": [
{
"category": "impact",
"details": "Important"
}
],
"title": "security flaw"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.