Spamassassin needs updated to reflect security fixes

Bug #1856248 reported by chris pollock
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
spamassassin (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Confirmed
Undecided
Ubuntu Security Team
Xenial
Fix Released
Undecided
Ubuntu Security Team
Bionic
Fix Released
Undecided
Ubuntu Security Team
Disco
Fix Released
Undecided
Ubuntu Security Team
Eoan
Fix Released
Undecided
Ubuntu Security Team

Bug Description

lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04

apt-cache policy spamassassin
spamassassin:
  Installed: 3.4.2-0ubuntu0.18.04.1
  Candidate: 3.4.2-0ubuntu0.18.04.1

The current version of Spamassassin is 3.4.2, the newest version, 3.4.3 fixes two security issues:

CVE-2019-12420 for Multipart Denial of Service Vulnerability

CVE-2018-11805 for nefarious CF files can be configured to
run system commands without any output or errors.

Request that Spamassassin be updated to the latest version 3.4.3 as soon as possible.

CVE References

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Chris,
thanks for your report.
I checked the security Teams overview of those at
- https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-11805.html
- https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-12420.html

It seems they are still evaluating the options hence the status "needs Triage".
I'll assign this bug to ubuntu-security so that they can update this bug along whatever they decide on the CVE triaging.

Changed in spamassassin (Ubuntu):
status: New → Confirmed
assignee: nobody → Ubuntu Security Team (ubuntu-security)
status: Confirmed → Fix Released
assignee: Ubuntu Security Team (ubuntu-security) → nobody
Changed in spamassassin (Ubuntu Trusty):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Changed in spamassassin (Ubuntu Xenial):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Changed in spamassassin (Ubuntu Bionic):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Changed in spamassassin (Ubuntu Disco):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Changed in spamassassin (Ubuntu Eoan):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

@Chris - security team told me on IRC on Friday that they will take a look as part of their normal triage.
To be on the safe side lets ping here again.

*ping*

Revision history for this message
chris pollock (cpollock) wrote :

Thanks Christian, appreciate the update.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in spamassassin (Ubuntu Bionic):
status: New → Confirmed
Changed in spamassassin (Ubuntu Disco):
status: New → Confirmed
Changed in spamassassin (Ubuntu Eoan):
status: New → Confirmed
Changed in spamassassin (Ubuntu Trusty):
status: New → Confirmed
Changed in spamassassin (Ubuntu Xenial):
status: New → Confirmed
Revision history for this message
chris pollock (cpollock) wrote :

I received an update to Spamassassin today however it was only to

 apt-cache policy spamassassin
spamassassin:
  Installed: 3.4.2-0ubuntu0.18.04.2
  Candidate: 3.4.2-0ubuntu0.18.04.2

The installed version I had prior to this was 3.4.2-0ubuntu0.18.04.1. Why wasn't this updated to the current version 3.4.3 as I stated in my initial bug report?

Changed in spamassassin (Ubuntu Eoan):
status: Confirmed → Fix Released
Changed in spamassassin (Ubuntu Disco):
status: Confirmed → Fix Released
Changed in spamassassin (Ubuntu Bionic):
status: Confirmed → Fix Released
Changed in spamassassin (Ubuntu Xenial):
status: Confirmed → Fix Released
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Hello Chris, for both security updates and bug fixes we prefer to backport specific fixes for specific bugs rather than switch to new versions, as described in https://wiki.ubuntu.com/SecurityTeam/FAQ#Versions

Thanks

Revision history for this message
chris pollock (cpollock) wrote :

Got it Seth, thanks for the explanation.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.