Fix security issues with HTML mails #15
Open
+13
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ed HTML tags. This security issue was discussed on the Imp mailing list around 2025-03-21. The topic of the email thread was "Horde v 5.2.22 vulnerability – obfuscation via HTML encoding – XSS payload"
…spite user's preference not to load remote images. May have security consequences, too. This fixes an old bug from the Horde bug tracker, see https://bugs.horde.org/ticket/15122 As detailed in an article about yet another security issue there, the loading to remote images may have security implications. So this is a precaution to avoid any such issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a recent report on the Horde mailing list about an exploit currently being used to inject malicious Javascript into the browser when a user just views a specially crafted e-mail in Horde/Imp.
The first commit fixes this issue, the second one similar issue where a fix has been sitting in the traditional Horde bugtracker for years now and has not been merged.