• Catoblepas@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    8 days ago

    Per the article, the attack works by making you think you’re clicking CAPTCHAs and reduces the opacity of the auto login buttons you’re actually pressing.

      • Catoblepas@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        5
        ·
        8 days ago

        Then I guess your comment confused me because the attack doesn’t require the user to attempt to log in. Completing a CAPTCHA on a random page isn’t internet idiot behavior, it’s what we’ve been trained to expect is the norm.

        • subignition@fedia.io
          link
          fedilink
          arrow-up
          1
          ·
          8 days ago

          I think I meant to reply to the user who was talking about KeePass. If you have brought the user to a malicious page, you can already just impersonate the login form and something like KeePass that doesn’t offer to autofill passwords will be none the wiser (because the user initiates the paste / autotype)

          In the XSS case, I think this would be occurring on a page the user trusts but has been compromised by an external script (via an ad or other means). If it’s at a domain the user has saved credentials for, odds are high it’s a login page, but I think you’re right that an attacker could probably add their own input field to provoke the password manager overlay, with an innocuous-looking fake captcha or cookie banner over it.