SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2022-47986Public Intelligence Dossier
Source: ibm · Limited verification•Last verified: •Collection Degraded
CVE-2022-47986ListedCRITICAL (raw)CVSS 9.8CWE-502

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

Published: 17 Feb 2023•Last updated: 17 Jun 2026, 10:44 AM IST•Source identifier: psirt@us.ibm.com
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added21 Feb 2023
Due14 Mar 2023
RansomwareKnown
CVSS score
9.8CRITICAL (raw)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Metric sourcepsirt@us.ibm.com
EPSS probability
100%1.000
Percentile100th
Weakness type
CWE-502
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; Microsoft or Microsoft-managed product relevance; CRITICAL severity; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • ibm aspera faspex · <= 4.4.1; 4.4.2 · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*, cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply updates per vendor instructions.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply updates per vendor instructions.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); deserialization (CWE-502)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Find installations of the affected component and confirm the source-stated version range.Telemetry: Application inventory · Deserialization risk requires component and version evidence. · Rule deserialization

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review unusual child processes or network connections from the affected service.Telemetry: DeviceProcessEvents · Unexpected behavior may support investigation but is not proof by itself. · Rule deserialization

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
21 Feb 2023
Required action due
14 Mar 2023
Known ransomware use
Known

Apply updates per vendor instructions.

Change History & Source Data

— No recorded material change

CNA / source
psirt@us.ibm.com
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:a:ibm:aspera_faspex:*:*:*:*:*:*:*:*, cpe:2.3:a:ibm:aspera_faspex:4.4.2:-:*:*:*:*:*:*, cpe:2.3:a:ibm:aspera_faspex:4.4.2:patch_level_1:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*, cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*

Evidence & Provenance

4 public sources
CISA KEV CatalogAdded 2023-02-21exchange.xforce.ibmcloud.comSource recordnvd.nist.govSource recordibm.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2022-47986
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2022-47986
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2022-47986"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.