almanah does not encrypt its database

2013.03.13
Credit: Vincent Danen
Risk: High
Local: No
Remote: Yes
CVE: CVE-2013-1853
CWE: CWE-310


CVSS Base Score: 2.1/10
Impact Subscore: 2.9/10
Exploitability Subscore: 3.9/10
Exploit range: Local
Attack complexity: Low
Authentication: No required
Confidentiality impact: Partial
Integrity impact: None
Availability impact: None

It was reported that Almanah does not encrypt its database when it closes, due to GApplication no longer using the quit_main_loop() event since GIO 2.32. This will keep the database unencrypted when it should be encrypted. The upstream bug report has a patch attached which corrects the issue. References: https://bugzilla.gnome.org/show_bug.cgi?id=695117 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702905 https://bugzilla.redhat.com/show_bug.cgi?id=920848

References:

https://bugzilla.gnome.org/show_bug.cgi?id=695117
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702905
https://bugzilla.redhat.com/show_bug.cgi?id=920848


See this note in RAW Version
Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}
Copyright 2024, cxsecurity.com

 

Back to Top