LiveActive security incident?Get immediate response
CVE Record

CVE-2000-1052: Allaire JRun 2.3 server allows remote attackers to obtain source code for executable content by directly ca...

Allaire JRun 2.3 server allows remote attackers to obtain source code for executable content by directly calling the SSIFilter servlet.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A very old flaw in Allaire JRun 2.3, a Java web application server from 2000, let anyone on the internet request source code for server-side pages by calling a specific built-in component directly. Exposing source code can leak business logic, hardcoded credentials, and database details. The product is long out of support, so the practical risk today is only for organizations still running legacy JRun 2.3 systems. Exposure is limited to environments still running Allaire JRun 2.3, a product Macromedia and later Adobe discontinued years ago. Any remaining instance is likely embedded in legacy internal or appliance systems. Internet-facing exposure would be unusual in 2026 but is a serious finding if discovered during discovery or M&A due diligence. Low priority for most modern estates because Allaire JRun 2.3 predates current infrastructure. Priority becomes high only if inventory confirms a live JRun 2.3 instance, especially one exposed externally or hosting business-critical logic. Treat any confirmed instance as end-of-life technical debt requiring a migration plan. Mitigation focus: Retire or replace Allaire JRun 2.3; the product line is end-of-life with no vendor patches available.; If retirement is not immediate, restrict access to JRun servers to trusted internal networks only.; Block external requests to the SSIFilter servlet path at the reverse proxy or WAF..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2000-1052 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.