# CVE-2018-10813: Hardcoded credentials in n/a

> Hardcoded session secrets in Dedos-web allow attackers to forge cookies, leading to privilege escalation and account takeover.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fpc8-954c-r7pq

## What is CVE-2018-10813?

CVE-2018-10813 is a high-severity vulnerability in n/a, published on 5 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Dedos-web 1.0, the cookie and session secrets used in the Express.js application have hardcoded values that are visible in the source code published on GitHub. An attacker can edit the contents of the session cookie and re-sign it using the hardcoded secret. Due to the use of Passport.js, this could lead to privilege escalation.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2018-10813?

It affects 1 product.


Products: Aprendecondedos Dedos-Web.

## How do I fix CVE-2018-10813?

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

## Is CVE-2018-10813 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10813 and fix it if it is affected.

What it is: CVE-2018-10813 is a high-severity vulnerability in n/a, published on 5 Jun 2018. 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-2018-10813 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-2018-10813/ (Markdown: https://insights.sbomify.com/CVE-2018-10813/index.md)
```

## Sources

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

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