# CVE-2023-6144: Dev Blog v1.0 - ATO

> Attackers can take over any user account by manipulating the user cookie, requiring only the target username.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 20 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-w9wh-97qp-xq2v

## What is CVE-2023-6144?

CVE-2023-6144 is a critical authentication bypass vulnerability in Dev Blog, published on 20 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dev blog v1.0 allows to exploit an account takeover through the "user" cookie. With this, an attacker can access any user's session just by knowing their username.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2023-6144?

It affects 1 product.


Products: Armanidrisi Dev Blog.

## How do I fix CVE-2023-6144?

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

## Is CVE-2023-6144 being exploited?

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

## Other vulnerabilities in Dev Blog

- [CVE-2023-6142](https://insights.sbomify.com/CVE-2023-6142/): Dev Blog v1.0 - Stored XSS (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6144 and fix it if it is affected.

What it is: CVE-2023-6144 is a critical authentication bypass vulnerability in Dev Blog, published on 20 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6144 in the wild and no public exploit code.

Affected product: Dev Blog. 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-2023-6144/ (Markdown: https://insights.sbomify.com/CVE-2023-6144/index.md)
```

## Sources

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

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