VulnerabilityPublished 11 Nov 2024Updated 19 Nov 2024

CVE-2024-48939: net2 · Insecure Storage of Sensitive Information

Affects net2Source CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 6.07.14023.5015 soon.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.07.14023.5015

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

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

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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2024
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

Upgrade paxton/net2 to 6.07.14023.5015.

Affected software

Product	Affected	Fixed in
GitHubpaxton/net2`pkg:github/paxton/net2`Other threats	Affected <6.07.14023.5015	Fixed in 6.07.14023.5015

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate upgrade to Paxton Net2 version 6.07.14023.5015 (SR4) or later once official patches are released to ensure proper license file validation.
If you cannot patch yet, restrict network access to the REST API by implementing strict firewall rules and network segmentation, allowing only trusted management systems to communicate with the API.
Monitor REST API traffic for unusual or unauthorized requests, especially those attempting to use invalid license files or retrieve access logs.
Implement strong access controls and authentication mechanisms around the management interfaces to reduce exposure.
Conduct regular audits of access logs and system configurations to detect anomalies indicative of exploitation attempts.
Engage with Paxton support or vendors for interim mitigation advice and to receive timely updates on patch availability.
Educate security and IT teams about this vulnerability to ensure rapid response and containment if exploitation is suspected.
Consider deploying intrusion detection/prevention systems (IDS/IPS) with custom signatures to detect attempts to exploit this license validation flaw.

Description

Insufficient validation performed on the REST API License file in Paxton Net2 before 6.07.14023.5015 (SR4) enables use of the REST API with an invalid License File. Attackers may be able to retrieve access-log data.

Impact

The primary impact of CVE-2024-48939 is the unauthorized disclosure of sensitive access-log data, which can include detailed records of physical access events, user identities, timestamps, and potentially other security-relevant metadata. This exposure can lead to privacy violations, facilitate further targeted attacks, or enable adversaries to map physical security layouts and user behaviors. Since the vulnerability requires no authentication and can be exploited remotely, it significantly increases the attack surface of affected organizations. The compromise of access logs undermines the integrity of security monitoring and incident response processes, as attackers may gain insights into security operations or cover their tracks. Organizations relying on Paxton Net2 for physical security management, such as corporate offices, government facilities, healthcare institutions, and critical infrastructure, face elevated risks of espionage, insider threat facilitation, or regulatory non-compliance due to data breaches. The absence of known exploits currently limits immediate widespread impact, but the vulnerability’s characteristics make it a likely target for future exploitation.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.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

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 00:21 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats