Bug 1215788 (CVE-2023-42118) - VUL-0: CVE-2023-42118: libspf2 Integer Underflow Remote Code Execution Vulnerability
Summary: VUL-0: CVE-2023-42118: libspf2 Integer Underflow Remote Code Execution Vulner...
Status: REOPENED
Alias: CVE-2023-42118
Product: openSUSE Distribution
Classification: openSUSE
Component: Security (show other bugs)
Version: Leap 15.6
Hardware: Other Other
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/380209/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-28 06:38 UTC by SMASH SMASH
Modified: 2023-10-19 09:41 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2023-09-28 06:38:01 UTC
This vulnerability allows network-adjacent attackers to execute arbitrary code
on affected installations of Exim libspf2. Authentication is not required to
exploit this vulnerability.

The specific flaw exists within the parsing of SPF macros. When parsing SPF
macros, the process does not properly validate user-supplied data, which can
result in an integer underflow before writing to memory. An attacker can
leverage this vulnerability to execute code in the context of the service
account.

06/06/22 – ZDI requested a PSIRT contact.

06/14/22 – ZDI reported the vulnerability to the vendor.

04/25/23 – ZDI asked for an update.

04/25/23 – The vendor asked us to re-send the reports.

05/10/23 – ZDI sent the vulnerability to the vendor.

09/25/23 – ZDI asked for an update and informed the vendor that we intend to
publish the case as a zero-day advisory on 09/27/23.

-- Mitigation: Given the nature of the vulnerability, the only salient
mitigation strategy is to restrict interaction with the application.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42118
Comment 1 Peter Wullinger 2023-10-02 06:00:01 UTC
Without further information, this looks more like a bug in libspf2 than in exim.
Comment 2 Peter Wullinger 2023-10-19 09:41:10 UTC
This is against libspf2, where efforts are still ongoing: https://github.com/shevek/libspf2/issues/45
Comment 3 Peter Wullinger 2023-10-19 09:41:36 UTC
keep open