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

CVE-2021-32018: n/a

Source CVE Database V5

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

8.5High

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

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

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

Attack Complexity: Low
Attack Vector: Network
Availability: Low
Confidentiality: High
Integrity: None
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
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: None: There is no loss of integrity within 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 2026-10-26.

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 verify if a patch or update is available from the JUMP AMS vendor and apply it promptly. 2. Access control: Restrict access to the JUMP SOAP API to trusted and authenticated users only, ideally limiting it to internal networks or VPNs. 3. Input validation: Implement additional server-side validation to sanitize and restrict file path inputs to prevent directory traversal attempts. 4. Monitoring and logging: Enable detailed logging of SOAP API requests and monitor for suspicious patterns indicative of directory traversal attempts. 5. Network segmentation: Isolate the JUMP AMS servers from critical infrastructure to limit lateral movement if exploitation occurs. 6. Credential management: Review and rotate credentials that may be stored or accessible via the vulnerable API to reduce risk from exposed files. 7. Incident response readiness: Prepare to respond quickly to any signs of exploitation, including forensic analysis and containment procedures. 8. Vendor engagement: Engage with the vendor for official guidance, patches, or mitigations and subscribe to security advisories for updates.

Description

An issue was discovered in JUMP AMS 3.6.0.04.009-2487. The JUMP SOAP API was vulnerable to arbitrary file reading due to an improper limitation of file loading on the server filesystem, aka directory traversal.

Impact

For European organizations using JUMP AMS 3.6.0.04.009-2487, this vulnerability poses a significant risk to the confidentiality of sensitive data. Exposure of configuration files, credentials, or other sensitive information could lead to unauthorized access to internal systems, data breaches, or escalation of privileges. Given the SOAP API is often used for integration and automation, exploitation could be performed remotely over the network, increasing the attack surface. The requirement for low privileges means that insider threats or compromised low-level accounts could exploit this vulnerability to gain access to critical information. This could impact sectors with high regulatory requirements for data protection, such as finance, healthcare, and government institutions in Europe. The scope change indicates that the vulnerability could affect multiple components or systems connected to the vulnerable API, potentially amplifying the impact. Although no known exploits are reported, the high CVSS score (8.5) and the nature of the vulnerability warrant immediate attention to prevent potential exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats