CVE-2021-3191
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 · uneditedIdelji Web ViewPoint Suite, as used in conjunction with HPE NonStop, allows Remote Unauthorized Access for T0320L01^ABY and T0320L01^ACD, T0952L01^AAR through T0952L01^AAX, and T0986L01^AAD through T0986L01^AAJ (L) and T0320H01^ABW through T0320H01^ACC, T0952H01^AAQ through T0952H01^AAW, and T0986H01^AAC through T0986H01^AAI (J and H).
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 confidenceIdelji Web ViewPoint Suite integration with HPE NonStop contains a remote unauthorized access vulnerability. The issue affects multiple T-number path variants across L, J, and H process types (T0320L01, T0952L01, T0986L01 and their H/J equivalents). An unauthenticated remote attacker can gain unauthorized access to the system through this vulnerability.
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>= 06.03, <= 06.23.01>= 15.08.00, <= 19.08.00>= t0320h01\^abw, <= t0320h01\^acc>= t0952h01\^aaq, <= t0952h01\^aaw>= t0952l01\^aar, <= t0952l01\^aax>= t0986h01\^aac, <= t0986h01\^aai>= t0986l01\^aad, <= t0986l01\^aaj= 15.02.00= 15.02.01= t0320l01\^aby= t0320l01\^acdCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 HPE Web Viewpoint installation versionLocate the installed HPE Web Viewpoint version on the system using standard version inspection methods for HPE software (typically via system inventory, software metadata, or version query commands for NonStop environments)Affected if The installed version falls within 06.03 through 06.23.01, 15.02.00, 15.02.01, or 15.08.00 through 19.08.00
-
Identify T-number path variant installationsSearch for the presence of T-number path components T0320, T0952, and T0986 in the Web ViewPoint configuration or installation directories on the NonStop systemAffected if Any of these T-number variants (T0320, T0952, T0986) are present in the installation
-
Determine process type variants in useInspect the specific T-number process variants to identify whether L, J, or H process type suffixes are configured (such as T0320L01, T0320H01, T0952L01, T0986L01 and their equivalents)Affected if The system uses L, J, or H process type variants of T0320, T0952, or T0986 paths
-
Check T-number version suffixesFor each identified T-number variant, inspect the version suffix (the alphanumeric code after the caret ^ symbol) to determine the specific build versionAffected if The T-number version suffix falls within the affected ranges: T0320L01^aar through ^aax, T0320H01^abw through ^acc, T0952L01^aar through ^aax, T0952H01^aaq through ^aaw, T0986L01^aad through ^aaj, T0986H01^aac through ^aai, or equals ^aby or ^acd for T0320L01
The environment is affected if HPE Web Viewpoint is installed with any of the vulnerable T-number path variants (T0320, T0952, T0986) in L, J, or H process types, and the specific version suffix falls within the documented affected ranges.
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 dataOrganizations using Idelji Web ViewPoint Suite with HPE NonStop should identify and patch the affected T-number path variants. Network segmentation and access controls should be applied to limit exposure until patches are applied.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3191 — 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-2021-3191 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