dbcve.org
Zxcloud GoldendbApplication · Zte

CVE-2025-46574

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-27
Fix available
A fix is available. Upgrade to 6.1.03.11 or later.
See remediation →
62/100
Remediation priority · Elevated
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
There is an information disclosure vulnerability in the GoldenDB database product. Attackers can exploit error messages to obtain the system's sensitive information.

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

GoldenDB database product contains an information disclosure vulnerability where error messages expose sensitive system information to attackers. This is a classic information leakage issue through verbose or improperly sanitized error outputs.

MitigationImplement proper error handling that returns generic error messages to users while logging detailed errors server-side. Sanitize or remove sensitive information from error message responses.

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
Zxcloud GoldendbApplication
Affected:>= 6.1.03, < 6.1.03.11= 7.2.01.01

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
Low
Integrity
None
Availability
None

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

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 GoldenDB version
    Run 'goldendb --version' or check the package/dBinary version installed on the system. On Linux, you may also check '/opt/goldendb/version' or look in the installation directory for a version file.
    Affected if The installed version is 6.1.03 or higher but below 6.1.03.11, OR the installed version is exactly 7.2.01.01
  2. Check for verbose error responses
    Trigger error conditions in the database by issuing malformed queries, accessing non-existent objects, or causing operational errors. Capture and inspect the HTTP/RPC response bodies or CLI output.
    Affected if Error responses contain stack traces, file paths, database internal names, system architecture details, or other sensitive system information rather than generic error codes
  3. Inspect error logging configuration
    Examine the GoldenDB configuration files (typically in /etc/goldendb/ or the installation conf/ directory) for 'error_detail', 'verbose_errors', 'stack_trace', or similar settings that control error verbosity.
    Affected if Debug or verbose error modes are enabled, or error output is set to 'detailed' rather than 'simplified' mode
  4. Review application error handling integration
    If GoldenDB is accessed via an application layer, test API endpoints or client connections to see if database errors propagate directly to end users without sanitization.
    Affected if Application-layer error messages expose database error codes, object names, or system details that should be internal only

You are affected if your GoldenDB version falls within 6.1.03 through 6.1.03.10, or is exactly 7.2.01.01, AND your error responses expose sensitive system information to users or clients.

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.1.03.11 or later
Fixed in 6.1.03.11
Interim mitigation

Implement proper error handling that returns generic error messages to users while logging detailed errors server-side. Sanitize or remove sensitive information from error message responses.

Recommended fix Moderate confidence

6.1.03.11 or later for 6.x branch; next stable release after 7.2.01.01 for 7.x branch

  1. 1. Identify the current GoldenDB version by checking the Zxcloud Goldendb installation
  2. 2. If running version 6.1.03.x where x < 11, plan upgrade to version 6.1.03.11 or later
  3. 3. If running version 7.2.01.01, plan upgrade to the next stable release after 7.2.01.01
  4. 4. Review ZTE support portal (support.zte.com.cn) for specific upgrade packages and migration guides
  5. 5. Schedule maintenance window for the upgrade process
  6. 6. Perform backup of database configurations and data
  7. 7. Execute upgrade following ZTE's official upgrade documentation
  8. 8. After upgrade, verify the system is operational and error messages no longer expose sensitive information
Caveat Minor version upgrades within the same major branch typically have backward compatibility, but always review ZTE release notes for any configuration or behavior changes before upgrading

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

Fix this in Zxcloud Goldendb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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