Bug 380034 - Possible exploit: If signed message has added arbitrary text in third line, Kleopatra doesnt warn user that "gpg: Invalid armor header:[content of line]"
Summary: Possible exploit: If signed message has added arbitrary text in third line, K...
Status: RESOLVED WORKSFORME
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-20 14:31 UTC by lurker69
Modified: 2022-12-06 05:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lurker69 2017-05-20 14:31:49 UTC
When verifying signed message in this format: https://pastebin.com/raw/yEiTHhvF 
anybody can insert any text in third line, and Kleopatra will verify message and not notify user that Header contained a line that should not be there. 


GPG2.exe or GPG in linux bash show warning:  
gpg: Invalid armor header: [inserted line] https://i.imgur.com/V28UTgJ.jpg

Kleopatra omits this warning and just shows green verification successful window.
https://i.imgur.com/0w3AasI.jpg


You can reproduce this with: 
https://pastebin.com/raw/yEiTHhvF  <--original unaltered
https://pastebin.com/raw/np4v7ZFM  <--altered message that also verifies in GUI but shows warning in command prompt 
https://pgp.mit.edu/pks/lookup?op=vindex&search=0x181F01E57A35090F
Comment 1 Justin Zobel 2022-11-06 09:25:36 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-21 05:13:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-06 05:19:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!