Code: Select all
NoScript detected a potential Cross-Site Scripting attack
from [...] to https://tempostorm.com.
Suspicious data:
(URL) https://tempostorm.com/{{ metaservice.ogMetaImage() }}
Code: Select all
NoScript detected a potential Cross-Site Scripting attack
from [...] to https://tempostorm.com.
Suspicious data:
(URL) https://tempostorm.com/{{ metaservice.ogMetaImage() }}
Does your FF open to a blank page, or the "hub" page where they show you a lot of links you may want to visit?JJ wrote:I keep getting a XSS warning every time I start firefox. It is from the same website. I went there once, but haven't been back. I'm worried I either got some sort of virus or this is a NoScript bug. Hopefully it is the later.
Code: Select all
NoScript detected a potential Cross-Site Scripting attack from [...] to https://tempostorm.com. Suspicious data: (URL) https://tempostorm.com/{{ metaservice.ogMetaImage() }}
Nope, XSS can happen without the malicious site being Allowed. IIRC NoScript Classic actually uses a stricter XSS filter for requests originating from untrusted sites, than for requests originating from trusted sites.Pansa wrote: it also means you gave [...] script permissions to begin with, because if it weren't allowed to run scripts, it wouldn't be allowed to crosscript to begin with.
barbaz wrote:Nope, XSS can happen without the malicious site being Allowed. IIRC NoScript Classic actually uses a stricter XSS filter for requests originating from untrusted sites, than for requests originating from trusted sites.Pansa wrote: it also means you gave [...] script permissions to begin with, because if it weren't allowed to run scripts, it wouldn't be allowed to cross-script to begin with.
See "link" for a short explanation of what XSS is.
That is exactly what I mean.Err, no, just about every site uses javascript from another domain and it's not an attack situation. XSS is when a malicious site injects its Javascript code into another site, e g your bank, and your bank site then runs the malicious code in its own context, i.e. as though the malicious site's injected code were part of the bank site's own code. Your browser is the vector for this injection.
I assume the [...] means a site he is not comfortable disclosing here.from [...] to storm
Nope. It literally says [...]/I assume the [...] means a site he is not comfortable disclosing here.
I am a bit confused now.Guest wrote:Nope. It literally says [...]/I assume the [...] means a site he is not comfortable disclosing here.
I get the same thing for a newspaper site (nrc.nl). For some reason it's always the same site:
This is the full text of the pop-up I keep getting.
---
NoScript detected a potential Cross-Site Scripting attack
from [...] to https://images.nrc.nl.
Suspicious data:
(URL) https://images.nrc.nl/mszTFGmkKoXHIjgT- ... 1/geld.png
---
Interestingly when I don't even have anything related to the newspaper site open.
This seems like a "linux" problem. There are some other threads about layout problems with linux/ubuntugrizzler wrote:NoScript's XSS handling is broken. On my system, it can't be switched off and keeps interfering as long as the add-on is installed, even if it's switched off in the add-on manager. On top op that, its popups are empty here. No text at all. I was forced to remove NoScript completely to be able to log in to a work related site.
I think you're on the money there. After having surfed a bit on other pages, the pop-up stopped happening from one page (nrc.nl), but started appearing for a different page! I have now disabled the 'starting page' content, and am no longer experiencing the issue.If they do that without you actually BEING on that page knowingly, either it is prefetching those pages (based on you already having been there (In which case the Firefox "starting page" may be the culprit