CVE-2019-3431
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 · uneditedAll versions up to V4.01.01.02 of ZTE ZXCLOUD GoldenData VAP product have encryption problems vulnerability. Attackers could sniff unencrypted account and password through the network for front-end system access.
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 · high confidenceThe ZTE ZXCLOUD GoldenData VAP product (versions up to V4.01.01.02) transmits user credentials in plaintext over the network. An unauthenticated remote attacker can sniff network traffic to intercept plaintext account usernames and passwords used for front-end system access.
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<= zxivs-vap-portal-xzgav4.01.01.02CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GoldenData VAP versionLocate the product version information in the ZTE ZXCLOUD GoldenData VAP installation. This is typically found in the system administration panel, About page, or by querying the portal service (zxivs-vap-portal-xzgav). Compare the installed version against the affected range: versions up to and including V4.01.01.02Affected if Installed version is zxivs-vap-portal-xzgav4.01.01.02 or earlier
-
Inspect network traffic during authenticationUse a network packet capture tool (such as tcpdump or Wireshark) to capture network traffic while performing a login to the GoldenData VAP front-end system. Filter for HTTP traffic on the authentication endpoint and examine the payload contentsAffected if User credentials (usernames and passwords) are visible in plaintext within the captured network packets
-
Check if HTTPS is enforced for authentication endpointsExamine the web server or application configuration for the GoldenData VAP portal. Verify whether the authentication endpoints are configured to redirect HTTP to HTTPS, and whether TLS/SSL is mandatory for all login-related trafficAffected if Authentication endpoints accept unencrypted HTTP connections or TLS/SSL is not enforced
-
Review SSL/TLS configuration for credential transmission pointsInspect the application configuration files and network settings to determine whether encryption is enabled for the paths that carry user credentials from the client to the serverAffected if Encryption (TLS/SSL) is disabled or not configured for credential transmission pathways
You are affected if your GoldenData VAP version is at or below V4.01.01.02 and network traffic analysis shows plaintext credentials during authentication, indicating unencrypted transmission.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement TLS/SSL encryption for all authentication pathways and sensitive network communications. Review and enable encryption for all account/password transmission points in the application.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3431 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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