dbcve.org
Easybuilder ProApplication · Weintek

CVE-2023-5777

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 6.07.02 / 6.08.01.614 or later.
See remediation →
100/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
Weintek EasyBuilder Pro contains a vulnerability that, even when the private key is immediately deleted after the crash report transmission is finished, the private key is exposed to the public, which could result in obtaining remote control of the crash report server.

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

Weintek EasyBuilder Pro contains a vulnerability where private keys used for crash report transmission are exposed to the public, even when deleted immediately after transmission completes. This key exposure could allow attackers to gain remote control of the crash report server.

MitigationContact Weintek for vendor patch; in the interim, disable or restrict crash report functionality, implement network segmentation, and monitor for indicators of compromise on crash report infrastructure.

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
Easybuilder ProApplication
Affected:< 6.07.02>= 6.08.01.190, < 6.08.01.614>= 6.08.02, < 6.08.02.500

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

CVSS:3.1/AV:N/AC:L/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 installed EasyBuilder Pro version
    Locate EasyBuilder Pro in the program directory or installed programs list and check the version number
    Affected if The installed version falls within < 6.07.02, >= 6.08.01.190 and < 6.08.01.614, or >= 6.08.02 and < 6.08.02.500
  2. Verify crash report feature is enabled
    Check EasyBuilder Pro settings or configuration for crash report or telemetry transmission options
    Affected if Crash report transmission functionality is turned on in the application settings
  3. Inspect crash report storage locations
    Search program data and application folders for crash report files or temporary folders that may contain residual private key files
    Affected if Any crash report related files or directories exist on the system, especially with key or certificate file extensions
  4. Review network connections to crash report infrastructure
    Monitor outbound connections from the machine to external IPs or domains associated with Weintek crash report servers
    Affected if Active or historical network connections to Weintek crash report servers are present
  5. Audit system for unauthorized access indicators
    Review logs on any crash report server infrastructure for unauthorized access attempts or unknown administrative accounts
    Affected if Signs of compromise such as unknown user accounts, modified configurations, or unexpected processes on crash report infrastructure are found

A user is affected if EasyBuilder Pro is installed with a version in the affected ranges AND crash report functionality is enabled, exposing private keys that could compromise the crash report server.

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 6.07.02 / 6.08.01.614 / 6.08.02.500 or later
Fixed in 6.07.026.08.01.6146.08.02.500
Interim mitigation

Contact Weintek for vendor patch; in the interim, disable or restrict crash report functionality, implement network segmentation, and monitor for indicators of compromise on crash report infrastructure.

Recommended fix High confidence

Upgrade to EasyBuilder Pro version 6.07.02, 6.08.01.614, 6.08.02.500 or later

  1. Identify the currently installed EasyBuilder Pro version via Help > About in the application
  2. Download the appropriate fixed version from the official Weintek website or trusted distribution channel
  3. Close any running instances of EasyBuilder Pro
  4. Run the installer for the fixed version (6.07.02, 6.08.01.614, or 6.08.02.500 and later)
  5. Follow the on-screen installation prompts to complete the upgrade
  6. Restart the application and verify the version under Help > About matches a fixed release
  7. If using a crash report server, ensure the private key configuration has been regenerated or replaced with a new, securely generated key

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

Fix this in Easybuilder Pro Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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