[Backport] CVE-2019-13675

Fixing extension corruption when navigating to extension resource with slash at end

Because of how Content Verifier currently normalizes relative paths of
an extension resource, it (incorrectly) drops any separators at the end
of the relative path. This makes Content Verifier incorrectly think
that a resource exists (if the separators came after a valid extension
resource path) and this results in content verification failure.

Fix this by ensuring content verifier path normalization does not drop
trailing separator, if present.

Bug: 929578

bar.html is present must not corrupt or disable the extension.

Test: Navigating to chrome-extension://<extensionId>/bar.html/ when
Change-Id: I3972643d9f9566e011070e4b01f0b1a50e3fa659
Commit-Queue: Utkarsh Patankar <utkpat@microsoft.com>
Auto-Submit: Utkarsh Patankar <utkpat@microsoft.com>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#667431}
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

0 files changed, 0 insertions, 0 deletions