<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for labels:"p1"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:55 -0000</lastBuildDate><item><title>XSS on wiki page and preview</title><link>https://forge-allura.apache.org/p/allura/tickets/7528/</link><description>Confirmed and reproduced here: https://sourceforge.net/p/strawhat/private-wiki/Swapnil_XSS/

***This also affects live wiki pages, not just the previews***

Original message from user,  Swapnil Thaware:

&gt;Respected Authorities,

&gt;My name is Swapnil A. Thaware and I am a Security Researcher from India. I have found security vulnerability in​ sourceforge.net. Here I am giving the details of the vulnerability found in sourceforge.net.


&gt;Vulnerability : Stored XSS

&gt;Vulnerability Description : Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted web sites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it.

&gt;An attacker can use XSS to send a malicious script to an unsuspecting user. The end user’s browser has no way to know that the script should not be trusted, and will execute the script. Because it thinks the script came from a trusted source, the malicious script can access any cookies, session tokens, or other sensitive information retained by the browser and used with that site. These scripts can even rewrite the content of the HTML page.

&gt;Step to Reproduce :
1) Login to Account
2) Goto wiki Section then Click on Create Page
3) Write a name
4) and then put XSS Payload in Content box then click on Preview button.
5) Boooommmm !! we get the popup

&gt;XSS Payload : 

~~~~
&lt;body onLoad=confirm(0)&gt; "&gt;&lt;svg/onload=alert(document.cookie)&gt; "&gt;"&lt;img src=x onerror=prompt(document.domain)&gt;"&gt; "&gt;&lt;ScRiPt&gt;alert("Hami Hax")&lt;%2FScRiPt&gt; "&gt;&lt;img src=x onerror=prompt('Xss');&gt; “&gt;&lt;img src=x onerror=alert(document.cookie)&gt; ';alert(String.fromCharCode(88,83,83))//';alert(String.fromCharCode(88,83,83))//"; alert(String.fromCharCode(88,83,83))//";alert(String.fromCharCode(88,83,83))//-- &gt;&lt;/SCRIPT&gt;"&gt;'&gt;&lt;SCRIPT&gt;alert(String.fromCharCode(88,83,83))&lt;/SCRIPT&gt;
~~~~


&gt;POC : I added a screenshot in attachment, please kindly check the attachment.


&gt;Kindly let me know when the vulnerability is fixed and I am eligible for any acknowledgement or any reward.​</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7528/</guid></item><item><title>XSS on /p/add_project/</title><link>https://forge-allura.apache.org/p/allura/tickets/6889/</link><description>[forge:site-support:#5930]

&gt;If yuo copy and past this payload: `"&gt;&lt;img src=x onerror=prompt(1);&gt;` at the page of soruceforge/p/add_Project in the two forms, you got a XSS

Not sure how exploitable that actually is, but following his instructions anyway I was able to reproduce that.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6889/</guid></item><item><title>Insecurity in Admin Overview Form [ss4721]</title><link>https://forge-allura.apache.org/p/allura/tickets/6469/</link><description>Hi All,

We have discovered a potential vulnerability in the project admin overview form at /admin/overview that could enable an attacker to inject custom html (including script tags) to anyone who visited that form page. The problem appears to be not limited to this form, but in every non-markdown textarea element on the site. Another example is in the milestone descriptions in the Ticket Admin Fields form at /admin//fields.

You can see an example at my project here: https://sourceforge.net/p/will/admin/overview, in which I have injected a simple js alert. However, prudence should preclude you from visiting that page, so I shall describe the exploit:

Within the Full Description textarea element, simply close the textarea tag, inject your own html, then open another textarea tag to round it out. This is what I put in:

~~~~
&lt;/textarea&gt;&lt;script&gt;alert("DOOM")&lt;/script&gt;&lt;textarea&gt;
~~~~

Once you put it in, make sure to reload the page, otherwise the browser will probably prevent the script from running after the post (at least chrome does).

In this case this attack is limited to those with admin rights to a project, but it nonetheless seems at least somewhat serious.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6469/</guid></item><item><title>Per-artifact ACLs not checked on _discuss URLs</title><link>https://forge-allura.apache.org/p/allura/tickets/5887/</link><description>https://sourceforge.net/p/forge/site-support/1658/ is set to private, but https://sourceforge.net/p/forge/site-support/_discuss/thread/d4066c48/ is accessible as an anonymous user.

We should check per-artifact ACLs for _discuss urls, or (perhaps even better), remove the _discuss URLs if they aren't used for anything.  That needs to be tested though - e.g. moderation might use them, I've seen them after a form submit that doesn't work (antispam spinner timeout)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5887/</guid></item></channel></rss>