New York Times nytimes.com Page Design XSS Vulnerability (Almost all
Article Pages Before 2013 are Affected)
Domain:
http://www.nytimes.com/
Vulnerability Description:
The vulnerability occurs at New York Times’s URLs. Nytimes (short for New
York Times) uses part of the URLs to construct its pages. However, it seems
that Nytimes does not filter the content used for the construction at all
before 2013.
Based on Nytimes’s Design, Almost all URLs before 2013 are affected (All
pages of articles). In fact, all article pages that contain “PRINT” button,
“SINGLE PAGE” button, “Page *” button, “NEXT PAGE” button are affected.
Nytimes changed this mechanism since 2013. It decodes the URLs sent to its
server. This makes the mechanism much safer now.
However, all URLs before 2013 are still using the old mechanism. This means
almost all article pages before 2013 are still vulnerable to XSS attacks. I
guess the reason Nytimes does not filter URLs before is cost. It costs too
much (money & human capital) to change the database of all posted articles
before.
Living POCs:
http://www.nytimes.com/2012/02/12/sunday-review/big-datas-impact-in-the-world.html/“>
http://www.nytimes.com/2011/01/09/travel/09where-to-go.html/“>?pagewanted=all&_r=0
http://www.nytimes.com/2010/12/07/opinion/07brooks.html/“>
http://www.nytimes.com/2009/08/06/technology/06stats.html/“>
http://www.nytimes.com/2008/07/09/dining/091crex.html/“>
http://www.nytimes.com/2007/11/14/opinion/lweb14brain.html/“>
POC Video:
https://www.youtube.com/user/tetraph
Vulnerability Analysis:
Take the following link as an example,
http://www.nytimes.com/2012/02/12/sunday-review/big-datas-impact-in-the-world.html/
“>