Bug 1699826 (CVE-2019-10734) - CVE-2019-10734 trojita: information disclosure of encrypted mail
Summary: CVE-2019-10734 trojita: information disclosure of encrypted mail
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2019-10734
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1699828 1699827
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-15 10:20 UTC by Dhananjay Arunesh
Modified: 2019-09-29 15:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:54:07 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 404697 0 None None None 2019-04-16 17:48:44 UTC

Description Dhananjay Arunesh 2019-04-15 10:20:22 UTC
In KDE Trojita 0.7, an attacker in possession of S/MIME or PGP encrypted emails
can wrap them as sub-parts within a crafted multipart email. The encrypted
part(s) can further be hidden using HTML/CSS or ASCII newline characters. This
modified multipart email can be re-sent by the attacker to the intended
receiver. If the receiver replies to this (benign looking) email, they
unknowingly leak the plaintext of the encrypted message part(s) back to the
attacker.

Reference:
https://bugs.kde.org/show_bug.cgi?id=404697

Comment 1 Dhananjay Arunesh 2019-04-15 10:22:54 UTC
Created trojita tracking bugs for this issue:

Affects: fedora-all [bug 1699827]

Comment 2 Dhananjay Arunesh 2019-04-15 10:23:17 UTC
Created trojita tracking bugs for this issue:

Affects: epel-7 [bug 1699828]

Comment 3 Product Security DevOps Team 2019-06-10 10:54:07 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.