# CVE-2024-48270: Denial of service in n/a

> Attackers can cause denial of service and access sensitive information in Oasys via a burst attack on the login component.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2024
- **Updated:** 4 Nov 2024
- **Also known as:** GHSA-3qxr-2r44-6w45

## What is CVE-2024-48270?

CVE-2024-48270 is a high-severity denial of service vulnerability in n/a, published on 1 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

## Which versions are affected by CVE-2024-48270?

It affects 1 product.


Products: Misstt123 Oasys.

## How do I fix CVE-2024-48270?

No fix has been published for CVE-2024-48270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-48270 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48270 exists.

## Other vulnerabilities in n/a

- [CVE-2025-3686](https://insights.sbomify.com/CVE-2025-3686/): misstt123 oasys show image path traversal (medium 5.3)
- [CVE-2025-3687](https://insights.sbomify.com/CVE-2025-3687/): misstt123 oasys Sticky Notes cross-site request forgery (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48270 and fix it if it is affected.

What it is: CVE-2024-48270 is a high-severity denial of service vulnerability in n/a, published on 1 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48270 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48270/ (Markdown: https://insights.sbomify.com/CVE-2024-48270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48270
- OSV: https://osv.dev/vulnerability/CVE-2024-48270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48270/
Summaries are generated and may contain mistakes; the official description above is the record.