Bug 70841 - konqueror ignores MAYSCRIPT keyword in APPLET tag
Summary: konqueror ignores MAYSCRIPT keyword in APPLET tag
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: kjava (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2003-12-19 15:01 UTC by Johannes Martin
Modified: 2018-10-27 02:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Martin 2003-12-19 15:01:23 UTC
Version:            (using KDE KDE 3.1.4)
Installed from:    Compiled From Sources

The (non-)existance of the MAYSCRIPT keyword in the APPLET tag specifies whether a Java applet is allowed to access form elements and JavaScript in a web page. If the keyword is absent, the Java applet is not allowed to communicate with JavaScript.

konqueror allows communication with JavaScript whether the tag is present or not. This is a potential security risk.
Comment 1 George Staikos 2003-12-19 15:07:57 UTC
Subject: Re:  New: konqueror ignores MAYSCRIPT keyword in APPLET tag

On Friday 19 December 2003 09:01, Johannes Martin wrote:
> The (non-)existance of the MAYSCRIPT keyword in the APPLET tag specifies
> whether a Java applet is allowed to access form elements and JavaScript in
> a web page. If the keyword is absent, the Java applet is not allowed to
> communicate with JavaScript.
>
> konqueror allows communication with JavaScript whether the tag is present
> or not. This is a potential security risk.

  How is this a security risk?  If someone wants to do bad things with Java, 
they could just exclude this MAYSCRIPT attribute altogether.  If this has to 
do with embedding other peoples' applets, well, I'm sure there are much worse 
things that can happen too.

Comment 2 Johannes Martin 2003-12-19 15:17:32 UTC
I did not say this was a horrible security risk that will make the world
end. The fact that we might not see bad implications at once, does not
mean there aren't any. I don't think the MAYSCRIPT keyword was introduced
just to annoy browser developers.
Comment 3 Johannes Martin 2004-07-09 10:49:02 UTC
This security risk still appears in KDE 3.2.3.
Comment 4 Tomas Trnka 2006-08-29 09:40:28 UTC
Yes, and what about a bit of standard compliance? The MAYSCRIPT attribute was NEVER defined in any of the HTML specifications (or in other words, it's a third-party extension, probably MS or Netscape, I don't know) and therefore I can't see any reasons why KHTML should implement/support it...Considering the APPLET element is deprecated since HTML 4...
Comment 5 Eric Kjeldergaard 2006-08-31 17:48:59 UTC
getting rid of unconfirmed bugs and this "problem" definitely exists.  In fact MAYSCRIPT even exists (in NS4, for instance).
Comment 6 Jaime Torres 2008-07-15 18:52:17 UTC
It looks like there is only one valid intersection between mozilla specs for MAYSCRIPT and W3C HTML standards....

http://www.w3.org/TR/REC-html40/struct/objects.html
http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guide/java_js.html

The use of <OBJECT>
     <PARAM NAME="code" VALUE="XYZApp.class">
     <PARAM NAME="codebase" VALUE="html/">
     <PARAM NAME="type" VALUE="application/x-java-applet;version=1.3">
     <PARAM NAME="MAYSCRIPT" VALUE="true">
</OBJECT>

In any case, this is not a security risk, in any case it is another problem for comunication between java and javascript for the web developer.
Comment 7 Myriam Schweingruber 2012-06-20 08:58:59 UTC
Does this still apply to Konqueror 4.8.4 or later?
Comment 8 Andrew Crouthamel 2018-09-23 02:44:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-10-27 02:33:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!