# CVE-2020-10511: HGiga C&Cmail - Broken Access Control

> Attackers can access unauthorized functionality in HGiga C&Cmail via crafted URLs due to insecure configurations, requiring an upgrade to secure versions.

- **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:** No
- **Published:** 15 Apr 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m4mj-5hcj-76vr

## What is CVE-2020-10511?

CVE-2020-10511 is a critical missing authorization vulnerability in HGiga C&Cmail, published on 15 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HGiga C&Cmail CCMAILQ before olln-base-6.0-418.i386.rpm and CCMAILN before olln-base-5.0-418.i386.rpm contains insecure configurations. Attackers can exploit these flaws to access unauthorized functionality via a crafted URL.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Hgiga Oaklouds Ccm\@il.

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

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

## Is CVE-2020-10511 being exploited?

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

## Other vulnerabilities in HGiga C&Cmail

- [CVE-2020-10512](https://insights.sbomify.com/CVE-2020-10512/): HGiga C&Cmail - SQL Injection (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10511 is a critical missing authorization vulnerability in HGiga C&Cmail, 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-10511 in the wild and no public exploit code.

Affected product: HGiga C&Cmail. 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-10511/ (Markdown: https://insights.sbomify.com/CVE-2020-10511/index.md)
```

## Sources

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

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