CVE-2024-48270VulnerabilityPublished 1 Nov 2024Updated 4 Nov 2024

CVE-2024-48270: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.1 base score

7.5High

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

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

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 1 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 2026-10-25.

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

Given the lack of an official patch, organizations should implement compensating controls immediately. These include restricting network access to the /logins endpoint through firewalls or web application firewalls (WAFs) to limit exposure to trusted IP ranges. Implement rate limiting and anomaly detection to identify and block burst attack patterns targeting login components. Conduct thorough monitoring and logging of access to sensitive endpoints to detect suspicious activity early. Review and harden authentication mechanisms and session management to reduce the impact of any leaked information. Engage with the Oasys vendor or community to obtain updates or patches as soon as they become available. Additionally, perform regular security assessments and penetration testing focused on authentication and information disclosure vectors. Educate security teams about this vulnerability to ensure rapid response if exploitation attempts are detected.

Description

An issue in the component /logins of oasys v1.1 allows attackers to access sensitive information via a burst attack.

Impact

The primary impact of CVE-2024-48270 is the unauthorized disclosure of sensitive information, which can lead to data breaches, identity theft, or further exploitation of compromised credentials. Organizations using Oasys v1.1 may face significant confidentiality losses, potentially exposing user credentials, personal data, or internal system information. This exposure can undermine trust, violate compliance requirements, and result in financial and reputational damage. Since the vulnerability does not affect integrity or availability, it does not directly enable data manipulation or denial of service, but the leaked information could facilitate subsequent attacks such as privilege escalation or lateral movement. The ease of exploitation without authentication or user interaction broadens the attack surface, increasing the likelihood of automated or opportunistic attacks. The absence of known exploits in the wild currently limits immediate risk but does not reduce the urgency for mitigation, as threat actors may develop exploits rapidly once details are publicized.

References

Community reviews

Loading reviews…