Closed Bug 1355213 Opened 9 years ago Closed 6 years ago

Don't allow WebExtensions to inject HTTP resources in HTTPS pages

Categories

(WebExtensions :: General, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1581611

People

(Reporter: jorgev, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [triaged])

Injecting plain HTTP images or scripts to HTTPS pages degrades their security and makes them show up as "mixed content" in Firefox. It's a reason for rejection during add-on code review. Filing this to see if it's something that can be blocked at the add-ons platform level.
will depend on bugs for applying CSP to content scripts - Kris comment
Flags: needinfo?(kmaglione+bmo)
Priority: -- → P2
Whiteboard: triaged
Depends on: 1267021
This depends on fixing bug 1267027. That would allow us to apply a different CSP depending on the principal that injected the content. We'd just need to add this restriction to that CSP for extension content scripts in HTTPS pages.
Assignee: nobody → kmaglione+bmo
Depends on: 1267027
No longer depends on: 1267021
Priority: P2 → --
Whiteboard: triaged
Flags: needinfo?(kmaglione+bmo)
Sorry, mid-aired.
Priority: -- → P2
Whiteboard: [triaged]
Product: Toolkit → WebExtensions
Component: Untriaged → General

Hey Shane, this seems something that could be part of what we want to look into as part of the extension content script CSP for manifest v3, would you mind to link it to the right meta?

Flags: needinfo?(mixedpuppy)

This probably just needs to be closed, it should be handled by the content script csp. Also bug 1594234 will generally prevent remote resources.

Assignee: kmaglione+bmo → nobody
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mixedpuppy)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.