Due to a lack of checking against intended target web addresses, malicious extensions are capable of changing where suggested links brought users when clicked on. This allows extensions to navigate users to malicious websites, or run Flash programs on the host device. Remote attackers could then use this to grab any file from the host device.
This vulnerability arose from the new functionality added to the NTP, where Chromium provides the user their most-visited sites and some suggested ones, without checking that the target of the link was the same as the link itself. Ultimately, this was a design mistake, because the developers never thought that such an attack would be possible, and while no exploit of this bug was ever created, it could have had huge consequences if it ever was. Additionally, between when the vulnerability was introduced and its fix, the subsystem was moved around, allowing the bug to hide longer than normal.
Hover over an event to see its title.
Click on the event to learn more.
Filter by event type with the buttons below.
Our curators found that this vulnerability was fixed by this commit.
The commit had 93 lines changed.
Here was the commit message.
NTP: don't allow navigateContentWindow to navigate where it pleases. BUG=509313 Review URL: https://codereview.chromium.org/1669723002 Cr-Commit-Position: refs/heads/master@{#373598}On the week starting on Monday, February 01, 2016, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 5 source code file(s). The impacted files were:
On the week of Monday, February 01, 2016, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, January 04, 2016, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 5 source code file(s). The impacted files were:
On the week of Monday, January 04, 2016, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, December 21, 2015, the code that was impacted by this vulnerability had 3 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week starting on Monday, December 07, 2015, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week of Monday, December 07, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, November 30, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, November 09, 2015, the code that was impacted by this vulnerability had 4 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, November 09, 2015, 2 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, September 28, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, September 21, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, September 21, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, September 07, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, August 31, 2015, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, August 31, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, August 03, 2015, the code that was impacted by this vulnerability had 3 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week of Monday, August 03, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, July 06, 2015, the code that was impacted by this vulnerability had 3 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 3 source code file(s). The impacted files were:
On the week of Monday, July 06, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, June 29, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, June 08, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, June 01, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, May 25, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, May 25, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, May 18, 2015, the code that was impacted by this vulnerability had 3 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, May 18, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, May 11, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, May 11, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, April 27, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, April 27, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, April 20, 2015, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, April 20, 2015, 1 commits mention the word "Refactor".
On the week starting on Monday, April 13, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, April 13, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, March 30, 2015, the code that was impacted by this vulnerability had 6 commit(s) by 4 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 3 source code file(s). The impacted files were:
On the week of Monday, March 30, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, March 23, 2015, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, March 23, 2015, 1 commits mention the word "Refactor".
On the week starting on Monday, March 16, 2015, the code that was impacted by this vulnerability had 3 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 3 source code file(s). The impacted files were:
On the week starting on Monday, March 09, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, March 09, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week of Monday, March 02, 2015, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, March 02, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, February 16, 2015, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 3 source code file(s). The impacted files were:
On the week starting on Monday, January 26, 2015, the code that was impacted by this vulnerability had 4 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, January 26, 2015, 2 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting Monday, January 26, 2015, an OWNERS file changed related to the vulnerable code.
This indicates a potential change in team structure and responsibilities.
On the week starting on Monday, January 12, 2015, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, December 22, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, December 22, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, December 08, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, December 08, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, November 17, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, November 17, 2014, 2 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting Monday, November 17, 2014, an OWNERS file changed related to the vulnerable code.
This indicates a potential change in team structure and responsibilities.
On the week starting on Monday, November 03, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, November 03, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, October 27, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, October 20, 2014, the code that was impacted by this vulnerability had 3 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, October 20, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, October 13, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, October 13, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week of Monday, October 06, 2014, 1 commits mention the word "Refactor".
On the week starting on Monday, October 06, 2014, the code that was impacted by this vulnerability had 3 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week of Monday, October 06, 2014, 2 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, September 22, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, September 22, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, September 15, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, September 15, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, August 25, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, August 25, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, August 18, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, August 18, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, August 11, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, August 04, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, July 21, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting Monday, July 21, 2014, an OWNERS file changed related to the vulnerable code.
This indicates a potential change in team structure and responsibilities.
On the week starting on Monday, July 14, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, July 07, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, July 07, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, June 30, 2014, the code that was impacted by this vulnerability had 9 commit(s) by 5 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 3 source code file(s). The impacted files were:
On the week of Monday, June 30, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting Monday, June 30, 2014, an OWNERS file changed related to the vulnerable code.
This indicates a potential change in team structure and responsibilities.
On the week starting on Monday, June 16, 2014, the code that was impacted by this vulnerability had 4 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 3 source code file(s). The impacted files were:
On the week of Monday, June 16, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, June 09, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, June 09, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, May 26, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, May 26, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, May 12, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, May 05, 2014, the code that was impacted by this vulnerability had 4 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 3 source code file(s). The impacted files were:
On the week of Monday, May 05, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, April 28, 2014, the code that was impacted by this vulnerability had 6 commit(s) by 5 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, April 28, 2014, 3 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting Monday, April 28, 2014, an OWNERS file changed related to the vulnerable code.
This indicates a potential change in team structure and responsibilities.
On the week starting on Monday, April 21, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, April 21, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, April 07, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, April 07, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, March 31, 2014, the code that was impacted by this vulnerability had 3 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, March 31, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, March 17, 2014, the code that was impacted by this vulnerability had 3 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, March 17, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, March 10, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, March 10, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, February 24, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, February 17, 2014, the code that was impacted by this vulnerability had 3 commit(s) by 3 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, February 17, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, February 10, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, February 03, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week starting on Monday, January 27, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week starting on Monday, January 20, 2014, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, January 20, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, January 13, 2014, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week of Monday, January 13, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, January 06, 2014, the code that was impacted by this vulnerability had 3 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week of Monday, January 06, 2014, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, December 23, 2013, the code that was impacted by this vulnerability had 3 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, December 16, 2013, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, December 16, 2013, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, December 09, 2013, the code that was impacted by this vulnerability had 9 commit(s) by 6 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 5 source code file(s). The impacted files were:
On the week of Monday, December 09, 2013, 2 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, December 02, 2013, the code that was impacted by this vulnerability had 2 commit(s) by 2 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week starting on Monday, November 25, 2013, the code that was impacted by this vulnerability had 4 commit(s) by 4 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 2 source code file(s). The impacted files were:
On the week of Monday, November 25, 2013, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, November 18, 2013, the code that was impacted by this vulnerability had 4 commit(s) by 4 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
On the week of Monday, November 18, 2013, 3 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week of Monday, November 18, 2013, 1 commits mention the word "Refactor".
On the week starting on Monday, November 11, 2013, the code that was impacted by this vulnerability had 5 commit(s) by 5 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 4 source code file(s). The impacted files were:
On the week of Monday, November 11, 2013, 1 developer(s) committed to this code, and they have never committed to this code before.
Learn more at Lesson: Too Many Cooks
On the week starting on Monday, November 04, 2013, the code that was impacted by this vulnerability had 1 commit(s) by 1 different developer(s), including 0 drive-by committer(s).
The commit had :notes~churn: lines changed.
Impacting a total of 1 source code file(s). The impacted files were:
A vulnerability-contributing commit (VCC) occurred here. This means that a curator identified this commit as (one of) the possible origins of this vulnerability.
This VCC had:
Thus it had a total raw churn of 334.
Here was the commit message.
The Vulnerability History Project
