CVE-2024-46622VulnerabilityPublished 6 Jan 2025Updated 7 Jan 2025

CVE-2024-46622: n/a

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical · fixed in 8.1.18 : patch affected systems as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.8Critical

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.1.18, 8.0.18, 7.1.11 +1

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

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

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

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).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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.
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).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jan 2025
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

AI-suggested

1. Immediate patching: Apply updates to SecureAge Security Suite as soon as vendor patches become available for versions 7.0.38, 7.1.11, 8.0.18, and 8.1.18 or later. 2. Restrict network exposure: Limit network access to systems running SecureAge Security Suite to trusted networks and hosts only, using firewalls and segmentation. 3. Implement strict file system permissions: Enforce least privilege on directories and files used by SecureAge to reduce the impact of arbitrary file operations. 4. Monitor file integrity: Deploy file integrity monitoring solutions to detect unauthorized creation, modification, or deletion of critical files. 5. Enhance logging and alerting: Enable detailed logging of SecureAge processes and file operations, and configure alerts for suspicious activities. 6. Conduct regular security audits: Review system configurations and access controls to ensure no unnecessary privileges are granted. 7. Prepare incident response: Develop and test response plans for potential exploitation scenarios involving privilege escalation and file tampering. 8. Educate administrators: Inform IT and security teams about the vulnerability and recommended defensive measures to ensure rapid response.

Description

An Escalation of Privilege security vulnerability was found in SecureAge Security Suite software 7.0.x before 7.0.38, 7.1.x before 7.1.11, 8.0.x before 8.0.18, and 8.1.x before 8.1.18 that allows arbitrary file creation, modification and deletion.

Impact

The impact of CVE-2024-46622 is severe for organizations worldwide using affected versions of SecureAge Security Suite. Successful exploitation allows attackers to escalate privileges without authentication, enabling arbitrary file operations that can compromise system integrity and confidentiality. This could lead to unauthorized access to sensitive data, installation of persistent malware, disruption of security controls, and potential full system takeover. The availability of critical security functions provided by SecureAge could be disrupted, increasing the risk of broader network compromise. Organizations in sectors with high security requirements such as finance, healthcare, government, and critical infrastructure face heightened risks due to the potential for data breaches and operational disruption. The vulnerability's network attack vector and lack of required privileges make it exploitable remotely, increasing the threat surface. The absence of known exploits currently provides a window for proactive defense, but the critical severity demands urgent attention to prevent exploitation.

Summary

CVE-2024-46622 is a critical security vulnerability classified as an escalation of privilege (CWE-281) affecting multiple versions of SecureAge Security Suite software prior to 7.0.38, 7.1.11, 8.0.18, and 8.1.18. This vulnerability enables an unauthenticated attacker to arbitrarily create, modify, and delete files within the system where the software is installed. The flaw arises from improper access control mechanisms within the SecureAge Security Suite, allowing attackers to bypass intended privilege restrictions. The vulnerability has a CVSS 3.1 base score of 9.8, reflecting its critical nature with network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and impacts on confidentiality, integrity, and availability (C:H/I:H/A:H). Exploitation could lead to full system compromise, data corruption, or denial of service. Although no public exploits have been reported yet, the vulnerability's characteristics suggest it could be weaponized quickly. The SecureAge Security Suite is used primarily for endpoint protection and data security, so this vulnerability undermines the security posture of affected systems. The lack of available patches at the time of disclosure necessitates immediate risk mitigation by organizations.

CWE-281Improper Preservation of Permissions (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 07:28 UTC

WeaknessesCWE-281

Technical details

References

Community reviews

Related threats