CVE-2021-22267
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 a remote replay attack for T0320L01^ABP through T0320L01^ABZ, T0952L01^AAH through T0952L01^AAR, T0986L01 through T0986L01^AAF, T0665L01^AAP, and T0662L01^AAP (L) and T0320H01^ABO through T0320H01^ABY, T0952H01^AAG through T0952H01^AAQ, T0986H01 through T0986H01^AAE, T0665H01^AAO, and T0662H01^AAO (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, deployed on HPE NonStop systems, contains a remote replay attack vulnerability affecting multiple transaction code ranges. An attacker can capture and replay valid authentication sequences to bypass authentication controls and gain unauthorized access to the system.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Locate the installed Idelji Web ViewPoint Suite versionOn the HPE NonStop system, check the product version using the command 'version -all' or inspect the Web ViewPoint installation directory for a version file. The version may also be displayed in the web interface login page footer or by accessing the /version endpoint if available.Affected if The installed version matches any of the following: 06.03 through 06.23.01, 15.02.00, 15.02.01, 15.08.00 through 19.08.00, or any t-prefixed version in the ranges t0320h01^abw through t0320h01^acc, t0952h01^aaq through t0952h01^aaw, t0952l01^aar through t0952l01^aax, t0986h01^aac through t0986h01^aa
-
Confirm the Web ViewPoint web interface is enabledVerify that the HTTP/HTTPS listener for Web ViewPoint is active on the NonStop system. Check process status using 'ps -ef' or the system management interface for any 'webviewp' or 'wvs' processes listening on ports 80, 443, or configured web ports.Affected if The web interface process is running and accessible, as the replay attack targets the authentication sequence transmitted through this interface.
-
Determine if authentication replay protection is implementedInspect the Web ViewPoint configuration files (typically in the config directory) for settings related to session token rotation, replay detection, or one-time authentication tokens. Look for parameters such as 'session_timeout', 'token_rotation', or 'replay_protection'.Affected if No replay protection mechanisms are configured, or the configuration shows static/fixed session tokens that do not change between authentication attempts.
-
Review authentication logs for duplicate session activityExamine Web ViewPoint authentication and session logs for entries showing identical session tokens or authentication sequences originating from different source IP addresses, which may indicate replay attacks.Affected if Logs contain multiple authentication attempts with identical session identifiers from different source addresses, confirming the vulnerability is exploitable in the environment.
A user is affected if Idelji Web ViewPoint Suite is running with a version matching any of the listed affected ranges and the web interface is exposed without replay attack mitigation in place.
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 dataApply vendor patches for Idelji Web ViewPoint Suite addressing the replay vulnerability. If no patch is available, implement compensating controls such as session token rotation, request replay detection, or network-level segmentation to mitigate the risk.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22267 — 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-22267 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