The issue is related to the `nsLocation::CheckURL` function, which does not properly follow the security model of the location object. This allows remote attackers to bypass intended content-loading restrictions, possibly having other unspecified impacts via vectors involving chrome code.