CVE-2019-19539
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 · uneditedAn issue was discovered in Idelji Web ViewPoint H01ABO-H01BY and L01ABP-L01ABZ, Web ViewPoint Plus H01AAG-H01AAQ and L01AAH-L01AAR, and Web ViewPoint Enterprise H01-H01AAE and L01-L01AAF. By reading ADB or AADB file content within the Installation subvolume, a Guardian user can discover the password of the group.user or alias who acknowledges events from the WVP Events screen.
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 confidenceIn Idelji Web ViewPoint, Guardian users can read ADB or AADB files within the Installation subvolume that contain plaintext or weakly protected passwords for group.user or alias accounts used to acknowledge events from the WVP Events screen. This allows privilege escalation through credential disclosure.
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>= t0320h01\^abo, <= t0320h01\^aby>= t0320l01\^abp, <= t0320l01\^abz>= t0952h01\^aag, <= t0952h01\^aaq>= t0952l01\^aah, <= t0952l01\^aar>= t0320l01\^abp, <= t0320l01\^abz>= t0986h01, <= t0986h01\^aaeCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Web ViewPoint installationLocate the Idelji or Hp Web ViewPoint application on the system and confirm its product name matches the affected softwareAffected if The product is not Web ViewPoint or the version cannot be determined as within the affected ranges
-
Determine installed versionRetrieve the exact version number of the Web ViewPoint installation (for example, from installation metadata, about screen, or version file) and compare it against the affected ranges: T0320 (t0320h01^abo through t0320h01^aby, or t0320l01^abp through t0320l01^abz), T0952 (t0952h01^aag through t0952h01^aaq, or t0952l01^aah through t0952l01^aar), T0986 (t0320l01^abp through t0320l01^abz, or t0986h01 through t0986h01^aae)Affected if The installed version falls within any of the listed affected ranges
-
Locate ADB/AADB filesSearch for files with .adb or .aadb extension within the Installation subvolume directory of the Web ViewPoint applicationAffected if ADB or AADB files exist in the Installation subvolume
-
Inspect credential storageOpen or read the ADB/AADB files and examine whether they contain plaintext passwords or weakly protected credentials for group.user or alias accounts used for WVP Events screen acknowledgmentAffected if The files contain plaintext or weakly protected passwords for group.user or alias accounts
-
Verify file permissionsCheck the access permissions on the ADB/AADB files to determine if unauthorized users other than intended administrators can read these filesAffected if File permissions allow non-administrative users to read the ADB/AADB files
A user is affected if they run a Web ViewPoint version within the specified ranges AND have ADB/AADB files in the Installation subvolume that are readable by non-admin users and contain plaintext or weakly protected credentials.
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 dataRestrict file system permissions on ADB/AADB files to prevent unauthorized access, implement proper password hashing/encryption for stored credentials, and rotate any compromised passwords.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19539 — 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-19539 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