# CVE-2020-11729: Weak cryptography in n/a

> Insecure generation of long-term session cookies in DAViCal AWL allows brute-force attacks leading to potential account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-11729, GHSA-9cpg-qfgf-gwq7, UBUNTU-CVE-2020-11729

## What is CVE-2020-11729?

CVE-2020-11729 is a critical vulnerability in Debian Debian Linux, published on 15 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in DAViCal Andrew's Web Libraries (AWL) through 0.60. Long-term session cookies, uses to provide long-term session continuity, are not generated securely, enabling a brute-force attack that may be successful.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2020-11729?

It affects 2 products.


Products: Davical Andrew\'s Web Libraries, Debian Debian Linux.

## How do I fix CVE-2020-11729?

Upgrade to a fixed version.

## Is CVE-2020-11729 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2020-11728](https://insights.sbomify.com/CVE-2020-11728/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11729 and fix it if it is affected.

What it is: CVE-2020-11729 is a critical vulnerability in Debian Debian Linux, published on 15 Apr 2020. 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-2020-11729 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2020-11729/ (Markdown: https://insights.sbomify.com/CVE-2020-11729/index.md)
```

## Sources

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

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