# CVE-2024-42013: Auth bypass in n/a

> Attackers with local admin or debug privileges can bypass password login in Blocky-Gui to gain full application access.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-f49h-cqg6-cgcc

## What is CVE-2024-42013?

CVE-2024-42013 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In GRAU DATA Blocky before 3.1, Blocky-Gui has a Client-Side Enforcement of Server-Side Security vulnerability. An attacker with Windows administrative or debugging privileges can patch a binary in memory or on disk to bypass the password login requirement and gain full access to all functions of the program.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2024-42013 being exploited?

There is no known exploitation of CVE-2024-42013 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42013 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42013 in the wild and no public exploit code.

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-42013/ (Markdown: https://insights.sbomify.com/CVE-2024-42013/index.md)
```

## Sources

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

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