IBM Aspera Faspex code execution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 4.4.2 PL2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
IBM Aspera Faspex, a file-transfer and exchange platform, is affected by this vulnerability. A remote attacker could exploit it to run arbitrary code on the affected system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
IBM Aspera Faspex 4.4.2 Patch Level 1 and earlier could allow a remote attacker to execute arbitrary code on the system, caused by a YAML deserialization flaw. By sending a specially crafted obsolete API call, an attacker could exploit this vulnerability to execute arbitrary code on the system. The obsolete API call was removed in Faspex 4.4.2 PL2. IBM X-Force ID: 243512.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- IBM Aspera Faspex
4.4.2 Patch Level 1 and earlier
References 3
ibm.com
exchange.xforce.ibmcloud.com
packetstormsecurity.com
Questions about CVE-2022-47986
What does this mean?
A flaw in an obsolete API call in IBM Aspera Faspex could allow a remote attacker to execute arbitrary code on the system.Source: ibm.com
Am I affected, and how do I check?
IBM Aspera Faspex 4.4.2 Patch Level 1 and earlier are affected, where the vulnerable obsolete API call is present. To check a installation, look at its reported Faspex version and patch level.Source: ibm.com
What should I do about it?
Upgrade to Faspex 4.4.2 PL2 or later, where the obsolete API call was removed. No workaround is listed in the facts.Source: ibm.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-02-21, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data