diff mbox series

[2/2] package/exim: mark CVE-2022-3620 as ignored

Message ID 20221202183631.2066307-2-peter@korsgaard.com
State Accepted
Headers show
Series [1/2] package/exim: add upstream security fixes for CVE-2022-3559 | expand

Commit Message

Peter Korsgaard Dec. 2, 2022, 6:36 p.m. UTC
CVE-2022-3620: A vulnerability was found in Exim and classified as
problematic.  This issue affects the function dmarc_dns_lookup of the file
dmarc.c of the component DMARC Handler.  The manipulation leads to use after
free.  The attack may be initiated remotely.  The name of the patch is
12fb3842f81bcbd4a4519d5728f2d7e0e3ca1445.  It is recommended to apply a
patch to fix this issue.  The associated identifier of this vulnerability is
VDB-211919.

This vulnerability is in the DMARC handling, which is only used if
libopendmarc is available AND SUPPORT_DMARC is set to yes, neither of which
is true for Buildroot, so ignore the CVE.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
 package/exim/exim.mk | 3 +++
 1 file changed, 3 insertions(+)

Comments

Thomas Petazzoni Dec. 3, 2022, 2:34 p.m. UTC | #1
On Fri,  2 Dec 2022 19:36:31 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:

> CVE-2022-3620: A vulnerability was found in Exim and classified as
> problematic.  This issue affects the function dmarc_dns_lookup of the file
> dmarc.c of the component DMARC Handler.  The manipulation leads to use after
> free.  The attack may be initiated remotely.  The name of the patch is
> 12fb3842f81bcbd4a4519d5728f2d7e0e3ca1445.  It is recommended to apply a
> patch to fix this issue.  The associated identifier of this vulnerability is
> VDB-211919.
> 
> This vulnerability is in the DMARC handling, which is only used if
> libopendmarc is available AND SUPPORT_DMARC is set to yes, neither of which
> is true for Buildroot, so ignore the CVE.
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/exim/exim.mk | 3 +++
>  1 file changed, 3 insertions(+)

We need to be careful to un-ignore this CVE if we enable DMARC support
before we bump to a newer release that has the CVE fixed. But
admittedly, it's unlikely that we will enable DMARC support anytime
soon.

Applied to master, thanks!

Thomas
Peter Korsgaard Dec. 7, 2022, 3:03 p.m. UTC | #2
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > CVE-2022-3620: A vulnerability was found in Exim and classified as
 > problematic.  This issue affects the function dmarc_dns_lookup of the file
 > dmarc.c of the component DMARC Handler.  The manipulation leads to use after
 > free.  The attack may be initiated remotely.  The name of the patch is
 > 12fb3842f81bcbd4a4519d5728f2d7e0e3ca1445.  It is recommended to apply a
 > patch to fix this issue.  The associated identifier of this vulnerability is
 > VDB-211919.

 > This vulnerability is in the DMARC handling, which is only used if
 > libopendmarc is available AND SUPPORT_DMARC is set to yes, neither of which
 > is true for Buildroot, so ignore the CVE.

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2022.08.x and 2022.02.x, thanks.
diff mbox series

Patch

diff --git a/package/exim/exim.mk b/package/exim/exim.mk
index cd2fabeab1..b84a51d6de 100644
--- a/package/exim/exim.mk
+++ b/package/exim/exim.mk
@@ -16,6 +16,9 @@  EXIM_DEPENDENCIES = host-berkeleydb host-pcre2 pcre2 berkeleydb host-pkgconf
 # 0006-Fix-regex-n-use-after-free.-Bug-2915.patch
 EXIM_IGNORE_CVES += CVE-2022-3559
 
+# built without dmarc support
+EXIM_IGNORE_CVES += CVE-2022-3620
+
 # Modify a variable value. It must already exist in the file, either
 # commented or not.
 define exim-config-change # variable-name, variable-value