Closed Bug 279101 Opened 20 years ago Closed 20 years ago

Security bug for internet banking (java application)

Categories

(Toolkit :: Form Manager, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: jan, Assigned: bugs)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 The bank uses a java application to ask for login information, such as a digital key of 4 digits among a possibility of 20 digits. With saved information active, Firefox keeps these entries and makes these visible. This is no problem for the loginid as such, but certainly for the 4 digit keyword. An example you can find here : http://www.argenta.be/frmst.asp?page=47&hoofdnav=6&subnav=5&dienstnav=&subsubnav=0 (and the push the entry "Start Internetbankieren") Reproducible: Always Steps to Reproduce: 1. Go to the internet banking page of www.argenta.be (use the url above) 2. Push the entry "Start Internetbankieren" 3. Go to an open entry digit on the last line ("Sleutelwoord") 3. Push the right mouse button followed by the left mouse button Actual Results: Secret key code digit numbers are displayed for all entered codes of the past for that field. Expected Results: Make it possible to disable this "save form option" by field or at least by form or webpage Similar to the Bug 252486, which is limited to https
They should have used autocomplete="off" in their field definition : <INPUT TYPE=password NAME=password SIZE=12 MAXLENGTH=12 value="" AUTOCOMPLETE="OFF">
I know they can solve the problem that way, but what if they refuse (what they actually did) because they just react by telling that they do not support Mozilla Firefox !!! If we as client would be able to put off autocompletion by web page, the problem would be solved without depending on the goodwill of the banks.
By the way the problem is not for the password itself, but for the randomly chosen 4 numeric digits out of a possibility of 16 numeric digits of the so called key word ("Sleutelwoord") in the last line of the login entry page. I already suggested them to treat these digits also as passwords like some other banks do, but no reaction yet.
Setting autocomplete=off at the server side can be over ridden by the user. Auto complete will appear to be off but the client app will still cache the field values. This is something that needs to be resolved by the developers of the browser, not the developers of the server side systems.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.