CampusinsightApplication · Huawei

CVE-2019-5278

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
There is an out-of-bounds read vulnerability in the Advanced Packages feature of the Gauss100 OLTP database in CampusInsight before V100R019C00SPC200. Attackers who gain the specific permission can use this vulnerability by sending elaborate SQL statements to the database. Successful exploit of this vulnerability may cause the database to crash.

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

An out-of-bounds read vulnerability exists in the Advanced Packages feature of the Gauss100 OLTP database in CampusInsight. Attackers with the specific required permissions can exploit this vulnerability by sending crafted SQL statements, causing the database to crash.

MitigationUpgrade CampusInsight to version V100R019C00SPC200 or later to obtain the patched Gauss100 OLTP database, or apply vendor-supplied patches.

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
CampusinsightApplication
Affected:= v100r019c00

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 CampusInsight installation
    Locate the CampusInsight installation directory or check for CampusInsight processes running on the system. On Linux, run 'ps -ef | grep -i campus' or check for installation directories like /opt/CampusInsight or similar. On the web interface, log in and navigate to the About or System Information page.
    Affected if CampusInsight is not installed on the system
  2. Check CampusInsight version
    Access the CampusInsight web interface and go to System > About, or run the command 'version' in the CampusInsight CLI if available. Alternatively, check installation logs or configuration files for the version string.
    Affected if The installed version is exactly v100r019c00 (this specific version is vulnerable)
  3. Verify Gauss100 OLTP database presence
    CampusInsight uses the Gauss100 OLTP database internally. Check if the gaussdb process or related database processes are running on the system using 'ps -ef | grep gauss' or by checking database configuration files.
    Affected if The Gauss100 OLTP database is not present or not in use by CampusInsight
  4. Confirm Advanced Packages feature accessibility
    The vulnerability exists in the Advanced Packages feature. Log into CampusInsight and navigate to check if the Advanced Packages functionality is available or enabled in the web interface or CLI. This feature is part of the database management tools.
    Affected if The Advanced Packages feature is not present or not accessible in your CampusInsight installation

You are affected if CampusInsight is installed with version v100r019c00 and the Advanced Packages feature of the Gauss100 OLTP database is accessible.

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 CampusInsight to version V100R019C00SPC200 or later to obtain the patched Gauss100 OLTP database, or apply vendor-supplied patches.

Fix this in Campusinsight Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5278 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5278 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