VulnerabilityPublished 3 Aug 2021Updated 30 May 2025

CVE-2021-32017: JUMP AMS 3.6.0.04.009-2487

Source CVE Database V5

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

9.9Critical

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

EPSS: 0.8% chance of exploitation in 30 days – higher than 59% 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 or the CVSS exploit maturity 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

AI-suggested

Immediate mitigation should include restricting access to the vulnerable SOAP endpoint by implementing network-level controls such as firewalls or VPNs to limit access only to trusted internal users.
Apply strict authentication and authorization controls on the JUMP AMS SOAP services to ensure only authorized users can access sensitive endpoints.
Monitor and audit access logs for unusual or unauthorized requests to the SOAP endpoint to detect potential reconnaissance activity.
If possible, disable or remove the vulnerable SOAP endpoint until a vendor patch or update is available.
Conduct a thorough review of the server’s file system permissions and harden the operating system to minimize sensitive data exposure.
Implement network segmentation to isolate critical asset management systems from general user networks.
Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.
Educate system administrators and security teams about this vulnerability to ensure rapid detection and response to any exploitation attempts.

Description

An issue was discovered in JUMP AMS 3.6.0.04.009-2487. A JUMP SOAP endpoint permitted the listing of the content of the remote file system. This can be used to identify the complete server filesystem structure, i.e., identifying all the directories and files.

Impact

For European organizations, this vulnerability poses a significant risk, especially for those using JUMP AMS in critical infrastructure, manufacturing, or enterprise environments where asset management systems are integral. The ability to enumerate the full server file system can lead to exposure of sensitive configuration files, credentials, or intellectual property. This can result in data breaches, operational disruption, and potential compliance violations under GDPR if personal data is exposed. The critical CVSS score reflects the high likelihood of severe impact, including unauthorized data access and potential system compromise. Organizations in sectors such as manufacturing, utilities, and large enterprises that rely on JUMP AMS for asset management are particularly vulnerable. The vulnerability could also be leveraged as a foothold for lateral movement within networks, increasing the risk of widespread compromise. Given the lack of known exploits in the wild, proactive mitigation is essential to prevent exploitation by threat actors who may develop exploits in the future.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

Technical details

References

Community reviews

Related threats