Bug 480867 - Plasma Integration blocks websites powered by Imperva
Summary: Plasma Integration blocks websites powered by Imperva
Status: REPORTED
Alias: None
Product: plasma-browser-integration
Classification: Plasma
Component: Chrome (show other bugs)
Version: unspecified
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-04 20:03 UTC by faynealdan
Modified: 2024-02-04 20:03 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Imperva error screen on a fresh Chrome install with only the Plasma Integration extension added (48.21 KB, image/png)
2024-02-04 20:03 UTC, faynealdan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description faynealdan 2024-02-04 20:03:17 UTC
Created attachment 165546 [details]
Imperva error screen on a fresh Chrome install with only the Plasma Integration extension added

SUMMARY
Having the Plasma Integration extension installed causes websites powered by Imperva to fail to load after first navigation.

STEPS TO REPRODUCE
1. Create a new profile in Google Chrome or Brave Browser.
2. Install Plasma Integration in the new profile: https://chromewebstore.google.com/detail/plasma-integration/cimiefiiaegbelhefglklhhakcgmhkai
3. Navigate to a website that uses Imperva. For example: https://www.pokemon.com
4. Refresh the webpage.

OBSERVED RESULT
You get an error page stating that "This request was blocked by our security service"

EXPECTED RESULT
Website loads as expected.

SOFTWARE/OS VERSIONS
Windows: Windows 11 23H2

ADDITIONAL INFORMATION
This only occurs on newly visited sites *after* installing Plasma Integration. It's also persistent once you trigger it, even if you remove the extension. For testing, you should clear site data when you install or remove the extension if you've already visited the site. Also, I only have the extension on Windows 11 because I sync the extension to a Linux machine. I don't have access to Linux right now to test the bug there.