CVE-2021-32016VulnerabilityPublished 3 Aug 2021Updated 30 May 2025

CVE-2021-32016: n/a

Source CVE Database V5

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

9.9Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:N

Attack Complexity: Low
Attack Vector: Network
Availability: High
Confidentiality: High
Integrity: High
Privileges Required: Low
Scope: Changed
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Aug 2021
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =3.6.0.04.009-2487	Fixed in–

AI-suggested

1. Immediate patching: Organizations should seek official patches or updates from the JUMP AMS vendor. If unavailable, consider vendor support channels or community advisories for mitigation guidance. 2. Network segmentation: Isolate JUMP AMS servers from general network access, restricting SOAP endpoint exposure to trusted internal networks only. 3. Access control: Enforce strict authentication and authorization policies limiting access to the SOAP endpoint to only necessary users and systems. 4. Input validation and monitoring: Implement Web Application Firewalls (WAFs) or intrusion detection systems (IDS) to detect and block directory traversal patterns and suspicious file write attempts targeting the SOAP endpoint. 5. File integrity monitoring: Deploy tools to monitor critical filesystem locations for unauthorized changes or new files indicative of exploitation attempts. 6. Incident response readiness: Prepare for rapid containment and forensic analysis in case of compromise, including backup and recovery plans. 7. Least privilege principle: Ensure that the service account running JUMP AMS has minimal filesystem permissions to limit the impact of arbitrary file writes. 8. Logging and alerting: Enable detailed logging of SOAP endpoint activities and establish alerts for anomalous behavior related to file writes or command execution attempts.

Description

An issue was discovered in JUMP AMS 3.6.0.04.009-2487. A JUMP SOAP endpoint permitted the writing of arbitrary files to a user-controlled location on the remote filesystem (with user-controlled content) via directory traversal, potentially leading to remote code and command execution.

Impact

For European organizations using JUMP AMS 3.6.0.04.009-2487, this vulnerability poses a significant risk. Successful exploitation can lead to complete system compromise, data breaches, and disruption of business operations. Confidential data could be exfiltrated or manipulated, and attackers could deploy ransomware or other malware. The ability to write arbitrary files and execute commands remotely without user interaction increases the likelihood of automated attacks and worm-like propagation within networks. This is particularly concerning for critical infrastructure, government agencies, and enterprises relying on JUMP AMS for asset management or operational control. The vulnerability could also undermine compliance with GDPR and other data protection regulations due to potential unauthorized data access and processing. Given the critical severity and ease of exploitation, European organizations must prioritize detection and remediation to prevent potential espionage, sabotage, or financial loss.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:29 UTC

Technical details

References

Community reviews

Related threats