dbcve.org
Oaklouds Ccm\@ilApplication · Hgiga

CVE-2020-10512

HIGH · 8.8 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HGiga C&Cmail CCMAILQ before olln-calendar-6.0-100.i386.rpm and CCMAILN before olln-calendar-5.0-100.i386.rpm contains a SQL Injection vulnerability which allows attackers to injecting SQL commands in the URL parameter to execute unauthorized commands.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in HGiga C&Cmail email server (CCMAILQ and CCMAILN versions before olln-calendar-6.0-100.i386.rpm and olln-calendar-5.0-100.i386.rpm respectively). Attackers can inject malicious SQL commands through URL parameters, potentially allowing unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpgrade to patched versions (olln-calendar-6.0-100.i386.rpm for CCMAILQ and olln-calendar-5.0-100.i386.rpm for CCMAILN). Additionally, implement parameterized queries, apply input validation, and consider WAF rules as compensating controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Oaklouds Ccm\@ilApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify HGiga C&Cmail installation
    Locate and inspect the email server software on the system. Check for installed packages named 'olln-calendar' or 'CCMAIL' using the system package manager (e.g., rpm -qa | grep -i calendar or dpkg -l | grep -i ccemail).
    Affected if The system has HGiga C&Cmail (Oaklouds Ccm@il) installed and the version is CCMAILQ before olln-calendar-6.0-100 or CCMAILN before olln-calendar-5.0-100.i386.rpm
  2. Determine installed version
    Run the package query command specific to your Linux distribution to retrieve the exact version number of the olln-calendar package. For RPM-based systems: rpm -qa | grep olln-calendar. Compare the output version against 6.0-100 (for CCMAILQ) and 5.0-100 (for CCMAILN).
    Affected if The installed olln-calendar package version is lower than 6.0-100 (CCMAILQ) or lower than 5.0-100 (CCMAILN)
  3. Verify web interface exposure
    Check if the C&Cmail web interface is accessible externally. Inspect web server configuration files (typically in /etc/httpd/conf.d/ or /etc/nginx/conf.d/) for any virtual host definitions related to the email server.
    Affected if The web interface for C&Cmail is exposed and accessible via HTTP/HTTPS URLs, as the SQL injection vector is through URL parameters
  4. Inspect web access logs for suspicious URL parameters
    Review web server access logs (commonly in /var/log/httpd/ or /var/log/nginx/) for the C&Cmail application. Search for patterns that may indicate SQL injection attempts such as 'UNION SELECT', 'OR 1=1', or other SQL keywords in query string parameters.
    Affected if Logs contain requests with SQL syntax embedded in URL parameters targeting the C&Cmail application endpoints

A system is affected if it runs HGiga C&Cmail (Oaklouds Ccm@il) with olln-calendar versions below 6.0-100 (for CCMAILQ) or below 5.0-100 (for CCMAILN), and has the web interface exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched versions (olln-calendar-6.0-100.i386.rpm for CCMAILQ and olln-calendar-5.0-100.i386.rpm for CCMAILN). Additionally, implement parameterized queries, apply input validation, and consider WAF rules as compensating controls.

Fix this in Oaklouds Ccm\@il Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10512 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data