dbcve.org
Cbot CoreApplication · Cbot

CVE-2023-2885

HIGH · 8.1 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to 4.0.3.4 / 4.0.3.7 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Enforcement of Message Integrity During Transmission in a Communication Channel vulnerability in CBOT Chatbot allows Adversary in the Middle (AiTM). This issue affects Chatbot: before Core: v4.0.3.4 Panel: v4.0.3.7.

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

This is an improper message integrity vulnerability in CBOT Chatbot that allows an attacker positioned between the client and server (Adversary in the Middle) to intercept and potentially modify messages in transit. The issue stems from insufficient validation of message integrity during transmission, likely due to missing or weak cryptographic checks (e.g., improper HMAC, missing message signing, or inadequate TLS configuration).

MitigationUpgrade CBOT Chatbot to Core v4.0.3.4 or later and Panel v4.0.3.7 or later. Additionally, ensure all communication channels use proper TLS with mutual authentication and implement message-level integrity verification (such as HMAC signing).

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
Cbot CoreApplication
Affected:< 4.0.3.4
Cbot PanelApplication
Affected:< 4.0.3.7

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 CBOT Core installation and version
    Locate the CBOT Core installation directory and check the version information file or use the product's version command. Common locations include /opt/cbot or the program's main executable directory.
    Affected if The installed CBOT Core version is lower than 4.0.3.4
  2. Identify CBOT Panel installation and version
    Locate the CBOT Panel installation directory and check the version information file or use the product's version command. Check the program's about or version settings panel.
    Affected if The installed CBOT Panel version is lower than 4.0.3.7
  3. Inspect TLS configuration between client and server
    Examine the configuration files governing client-server communication. Look for TLS/SSL settings, certificate validation parameters, and whether mutual authentication (mTLS) is enabled.
    Affected if TLS is not configured with mutual authentication or uses weak/obsolete cipher suites
  4. Verify message-level integrity verification settings
    Inspect the message handling configuration to determine if HMAC signing or other cryptographic message integrity checks are enabled. Check configuration files related to message authentication.
    Affected if Message-level integrity verification (such as HMAC signing) is disabled or not implemented

A user is affected if they are running CBOT Core below version 4.0.3.4 or CBOT Panel below version 4.0.3.7 AND the communication channel lacks proper TLS with mutual authentication OR message-level integrity verification is not implemented.

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.

dbcve · scoped
Upgrade available Upgrade to 4.0.3.4 / 4.0.3.7 or later
Fixed in 4.0.3.44.0.3.7
Interim mitigation

Upgrade CBOT Chatbot to Core v4.0.3.4 or later and Panel v4.0.3.7 or later. Additionally, ensure all communication channels use proper TLS with mutual authentication and implement message-level integrity verification (such as HMAC signing).

Recommended fix High confidence

Cbot Core >= 4.0.3.4, Cbot Panel >= 4.0.3.7

  1. Backup your current Cbot Core and Cbot Panel installations and databases
  2. Upgrade Cbot Core to version 4.0.3.4 or later
  3. Upgrade Cbot Panel to version 4.0.3.7 or later
  4. Restart all Cbot services after upgrading
  5. Verify the upgrade was successful by checking the version numbers in the admin interface
  6. Test chatbot functionality to ensure normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cbot Core Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2885 — 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-2023-2885 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