r/Lastpass • • Aug 08 '18

LastPass is injecting javascript code into my eBay listings.

All of my latest eBay listings have js code injected into the item description.

Although I only installed LastPass last month for the first time (and therefore have the latest version), this has apparently been a problem for a while.

After checking numerous forum posts about the issue, LastPass seems entirely indifferent about fixing the problem.

Does anyone know if LastPass has a bugtracker?

Here is the code that is being injected:

<script>
try{
    (function() {
        if (typeof(lpcurruser) == 'undefined') lpcurruser = ''; 
        if (document.getElementById('lpcurruserelt') && document.getElementById('lpcurruserelt').value != '') { 
            lpcurruser = document.getElementById('lpcurruserelt').value; document.getElementById('lpcurruserelt').value = '';
        }
        if (typeof(lpcurrpass) == 'undefined') lpcurrpass=''; 
        if (document.getElementById('lpcurrpasselt') && document.getElementById('lpcurrpasselt').value != '') { 
            lpcurrpass = document.getElementById('lpcurrpasselt').value; document.getElementById('lpcurrpasselt').value = ''; 
        } 
        var lploc=1;
        var lponlyfill=1;
        (function() {
            var doc = document;
            var frm = doc.getElementById('SignInForm');
            var old_username = doc.getElementById('userid');
            var old_password = doc.getElementById('pass');
            var runids = doc.getElementsByName('runId2');
            var runid = null;
            if (runids.length==1) { 
                runid = doc.getElementsByName('runId2')[0]; 
            }
            if (frm && runid && old_username && old_password ) {
                try {
                    old_username.value = "";
                    old_password.value = "";
                    old_username.parentNode.nextSibling.getElementsByTagName('input')[0].value = lpcurruser;
                    old_password.parentNode.previousSibling.getElementsByTagName('input')[0].value = lpcurrpass;
                } 
                catch (e) { };
            }
        })();
        lpcurruser = ''; 
        lpcurrpass = '';
    })();
}
catch(e){}
</script>
0 Upvotes

4 comments sorted by

20

u/Richie4422 Aug 08 '18

Because it's not a bug and not an issue. LastPass injects javascript in to fields (like editing window) to provide features like - filling custom fields, detecting custom fields, notes, usernames or passwords.

If you don't want this happening on particular page, follow these steps:

  1. LastPass Vault

  2. Go to Account Settings

  3. Click on Never URLS

  4. Click. 'Add'

  5. Pick 'Never Do Anything' from the Menu

  6. Add bulksell.ebay.com/ws/eBayISAPI.dll (customize url to fit your region - aka co.uk, .ie)

  7. Click 'Add'

8

u/Web-Dude Aug 08 '18

It is absolutely an issue, and to any end-user it is absolutely a bug. When should a submitted form ever include injected javascript? Is LastPass hoping the backend system will just filter it out?

If you need to go through a seven-step process to make a plugin work the way it's supposed to, then it's a bug. Or at the very least, an oversight.

It could simply be handled by making the eBay url a pre-filled default.

17

u/Richie4422 Aug 08 '18

It is designed to work that way, hence it's not a bug.

For example, there was an actual issue of injecting onloadwff.js and LastPass fixed it.

LastPass simply doesn't have control over eBayISAPI.dll and LastPass certainly isn't going to change the way it handles fields just because of eBay.

The plugin works the way it's supposed to work. That 7 step process is simply a feature giving you the control over sites and when or if LastPass should handle them.

You are free to contact LastPass support if you feel so strong about it.