This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix($sanitize): sanitize
xml:base
attributes
On Firefox there is a XSS vulnerability if a malicious attacker can write into the `xml:base` attribute on an SVG anchor. Thanks to Masato Kinugawa at Cure23
- Loading branch information
1 parent
e06b4fb
commit b9ef658
Showing
2 changed files
with
10 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cure23 again... they are the worst, right?
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry!
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is reported as a security vulnerability by Snyk, shouldn't it have a CVE assigned to it?
https://snyk.io/vuln/npm:angular:20180202
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what you mean @JLLeitschuh. The Snyk refers to https://cwe.mitre.org/data/definitions/79.html
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@petebacondarwin It refers to a CWE which != CVE. CVE numbers are assignments for publicly disclosed vulnerabilities.
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://danielmiessler.com/blog/difference-cve-cwe/
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I think the answer to your original question is yes? Are there other CVEs assigned for AngularJS vulnerabilities?
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few, less than Snyk reports though. That doesn't mean there shouldn't be more though. Does the angular team collect vulnerability reports in a common location or are they scattered across all the release notes?
I'm just a vulnerability researcher poking at an angular based app and trying to find potential vulnerabilities in a target, but as a core contributor, you should probably be ensuring that things like this are properly reported/disclosed to the public via the CVE system.
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll find out what the policy is. Note that this project "AngularJS" is in LTS mode so is not actively worked on right now. The "Angular" project is the one being actively maintained. See https://github.com/angular/angular
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. Still, this is only a year and a half old and there are still lots of companies running old versions of Angular.
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/CC @rjamet might know, or might know someone who does :-)
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My team generally don't file for CVEs, but we're not against them being filed either, they're a really useful tool. I'm not familiar with the process to do so, but at a glance, it's easy enough to do: https://cveform.mitre.org/
b9ef658
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rjamet Please consider making it an official part of your disclosure process.
You can also use Snyk as a CNA. They may dig into the open source ecosystem a bit more to provide more detailed remediation information.
https://snyk.io/vulnerability-disclosure/