CVE-2003-1516: Medium severity Sun Java Plug-In vulnerability

Published Dec 31, 2003
·
Updated

The org.apache.xalan.processor.XSLProcessorVersion class in Java Plug-in 1.4.201 allows signed and unsigned applets to share variables, which violates the Java security model and could allow remote attackers to read or write data belonging to a signed applet.

Affected Software

1 affected component
Sun Java Plug-In=1.4.2_01

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Until a vendor-supplied fix is available, block or disable the Sun Java Embedding Plugin version 1.4.2_01 from running — e.g., disable the plugin in browsers, prevent execution of the plugin binary, or isolate hosts running that exact version.

  2. Operational

    Inventory your environment for instances of the Sun Java Embedding Plugin and identify any installations reporting version 1.4.2_01 (the org.apache.xalan.processor.XSLProcessorVersion class in Java Plug-in 1.4.2_01 is vulnerable).

Event History

Dec 31, 2003
CVE Published
05:00 AM
Data Sourced
via NVD·05:00 AM
DescriptionSeverityAffected Software
Oct 25, 2007
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2003-1516?

CVE-2003-1516 has been classified as a high-severity vulnerability due to its potential to allow unauthorized access to applet data.

2

How do I fix CVE-2003-1516?

To fix CVE-2003-1516, you should upgrade to a later version of the Java Plug-in that corrects this vulnerability.

3

What products are affected by CVE-2003-1516?

CVE-2003-1516 specifically affects Sun Java Plug-in 1.4.2_01.

4

What type of attack can CVE-2003-1516 facilitate?

CVE-2003-1516 can facilitate attacks that allow untrusted applets to read or write data belonging to trusted applets.

5

Is there a workaround for CVE-2003-1516?

Currently, the most effective workaround for CVE-2003-1516 is to avoid the use of the affected version of the Java Plug-in.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203