Document Title:  
KeeWeb v1.14.0 - (Notes) Html Inject Web Vulnerability  
References (Source):  
Release Date:  
Vulnerability Laboratory ID (VL-ID):  
Common Vulnerability Scoring System:  
Vulnerability Class:  
Script Code Injection  
Current Estimated Price:  
1.000€ - 2.000€  
Product & Service Introduction:  
Free cross-platform password manager compatible with KeePass. Web  
version has almost all features available in desktop apps.  
It doesn't require any installation and works in all modern browsers.  
Desktop apps look beautiful on each platform: macOS,  
Windows and Linux. You can open local files in Desktop apps.  
(Copy of the Homepage: &  
Abstract Advisory Information:  
The vulnerability laboratory core research team discovered a html  
injection web vulnerability in the KeeWeb v1.14.0 online service  
Affected Product(s):  
Product: KeeWeb v1.14.0 - Online Service (Web-Application)  
Product: KeeWeb v1.14.0 x64 - Windows Desktop Client (Software)  
Vulnerability Disclosure Timeline:  
2020-05-06: Public Disclosure (Vulnerability Laboratory)  
Discovery Status:  
Exploitation Technique:  
Severity Level:  
Authentication Type:  
Restricted authentication (user/moderator) - User privileges  
User Interaction:  
Medium User Interaction  
Disclosure Type:  
Independent Security Research  
Technical Details & Description:  
A html injection web vulnerability has been discovered in the official  
KeeWeb v1.14.0 online service web-application.  
The vulnerability allows remote attackers to inject own malicious html  
codes with persistent attack vector to compromise browser  
to web-application requests from the application-side.  
The html inject web vulnerability is located in the notes input field of  
the new entry add module. Local privileged accounts are able  
to compromise the stored database entries by inject of simple html code.  
After the inject the execution points of the issue are located  
in the New Entry or on export as HTML5 file. The execute occurs in both  
cases on review in the vulnerable marked fields of the input.  
The request method to inject is POST and the attack vector is located on  
the application-side. The issue is a classic html injection.  
There is already a poc exploit in the wild available with the expected  
client database format to import after the export.  
Successful exploitation of the web vulnerability results in persistent  
phishing attacks, persistent external redirects to malicious  
source and persistent manipulation of affected application modules.  
Request Method(s):  
[+] POST  
Vulnerable Module(s):  
[+] New  
Vulnerable Parameter(s):  
[+] Notes  
Affected Module(s):  
[+] New entries on preview  
[+] Export as HTML5 file  
Proof of Concept (PoC):  
The html inject web vulnerability can be exploited by remote attackers  
with privileged user account or via medium user interaction.  
For security demonstration or to reproduce the vulnerability follow the  
provided information and steps below to continue.  
Manual steps to reproduce the vulnerability ...  
1. Open the KeeWeb application  
2. Add a new Database  
3. Include a new entry  
4. Inject to the Notes input field your html payload with external request  
5. Save the entry and export the kdbx or as html5  
Note: The execution of the html code occurs on preview of the entry or  
open of the html file  
6. Successful reproduce of the vulnerability!  
PoC: Payload  
PoC: Vulnerable Source (Export HTML5)  
<div class="markdown"><blockquote>  
<tr><td>New Field</td>  
PoC: Exploit (kdbx - aes encrypted) (passwd:test)  
Ù¢šgûKµ 1Áòæ¿qCP¾X!jüZÿ   
A¶C½3âÀ¥éWí>P9-C5sÍj™P‚yå à“ nhÉOTÇQMÜ3Ñë.  
FÓjh·‡Õ'Ê,®}&èo nyü¢.½üõ2=§Ô® @:¸æZEJ]Ö,<RÄh  
>Ó ¬¯ct«’l"ŠãMga.OkðvéÉ4?]ÚJ&ƒèðµ¶t!U|kM -ÎÕã+  
ZÖÖDít½¦4¬´óŽåG冖®¢Ë¥°ëœßójj¬cW2¹* ³µ± ¯¿3fÒ#  
¹ëK5%õQ,Dô7¡Øwa-Qš–æ.ÌÏ Eó,] 4mnýì–¥¦89³âÁn첚ÄmÔã<""þh^]ü  
’ΤC gaLœ®ä+.úíæE`î  
êö›s…j@W¨z ñ#ŠX/2ã¬Êj  
4Ò¸R0#|€K¹Ï‚®NMot¯@GØ]ª’ßëÙˆðé8š2.F@ç½ú$-ÏsÀaŸÉpÍã ˆ$՛Š 
;sPÀŠü1&z}£1Ý;昒QuœÃ™½-*†°ÑÌ»AP͘:ÍÁ³%¤ Ž2«Vî~|–bds9.  
ºR*k­.îrÿã»<|Ðx_±jÃvyù¢êoì¶ugF·u'Š£Cr‹F+dt ËtÃÒM} ”­°jÚbå¼ìjY‰¿˜¤cšb  
Solution - Fix & Patch:  
The vulnerability can be resolved by an encode of the vulnerable output  
parameters in the html5 files on export.  
In a second step the input fields of the notes and others needs to be  
restricted to disallow script code injects  
The notes parameter needs to be escaped to ensure the injection point is  
Credits & Authors:  
Vulnerability-Lab -  
Benjamin Kunz Mejri -  
Disclaimer & Information:  
The information provided in this advisory is provided as it is without  
any warranty. Vulnerability Lab disclaims all warranties,  
either expressed or implied, including the warranties of merchantability  
and capability for a particular purpose. Vulnerability-Lab  
or its suppliers are not liable in any case of damage, including direct,  
indirect, incidental, consequential loss of business profits  
or special damages, even if Vulnerability-Lab or its suppliers have been  
advised of the possibility of such damages. Some states do  
not allow the exclusion or limitation of liability for consequential or  
incidental damages so the foregoing limitation may not apply.  
We do not approve or encourage anybody to break any licenses, policies,  
deface websites, hack into databases or trade with stolen data.  
Any modified copy or reproduction, including partially usages, of this  
file requires authorization from Vulnerability Laboratory.  
Permission to electronically redistribute this alert in its unmodified  
form is granted. All other rights, including the use of other  
media, are reserved by Vulnerability-Lab Research Team or its suppliers.  
All pictures, texts, advisories, source code, videos and other  
information on this website is trademark of vulnerability-lab team & the  
specific authors or managers. To record, list, modify, use or  
edit our material contact (admin@ or research@) to get a ask permission.  
Copyright © 2020 | Vulnerability Laboratory - [Evolution  
Security GmbH]™