CVE-2022-37931
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 · uneditedA vulnerability in NetBatch-Plus software allows unauthorized access to the application. HPE has provided a workaround and fix. Please refer to HPE Security Bulletin HPESBNS04388 for details.
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 confidenceThis vulnerability in HPE NetBatch-Plus allows unauthorized access to the application. The CVSS 7.8 score indicates high exploitability, likely due to an authentication bypass or weak credential mechanism in the software.
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>= t9189h01, < t9189h01\^abw>= t9189l01, < t9189l01\^abyCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Confirm HPE NetBatch-Plus installationLocate the NetBatch-Plus installation directory or check system inventory for NetBatch-Plus packages. On NonStop systems, this may involve checking the installation path or using system management tools.Affected if NetBatch-Plus is not installed on the system
-
Retrieve installed NetBatch-Plus versionUse the appropriate command or tool to query the NetBatch-Plus version. On NonStop systems, this may involve checking the version attribute of the NetBatch-Plus process or examining the product documentation for version retrieval methods.Affected if Unable to determine the version or NetBatch-Plus is not found
-
Compare version against first affected rangeCheck if the installed version starts with t9189h01 and is less than t9189h01 with the ^abw suffix applied. Versions between t9189h01 (inclusive) and t9189h01^abw (exclusive) are affected.Affected if Version begins with t9189h01 and is lower than t9189h01^abw
-
Compare version against second affected rangeCheck if the installed version starts with t9189l01 and is less than t9189l01 with the ^aby suffix applied. Versions between t9189l01 (inclusive) and t9189l01^aby (exclusive) are affected.Affected if Version begins with t918l01 and is lower than t918l01^aby
-
Assess network accessibilityDetermine if the NetBatch-Plus application is exposed to network access. Check firewall rules, access controls, and whether the application listens on accessible network interfaces.Affected if NetBatch-Plus is network-accessible and version falls within affected ranges
The environment is affected if HPE NetBatch-Plus is installed with a version matching t9189h01 up to (but not including) t9189h01^abw, or t9189l01 up to (but not including) t9189l01^aby, and the application is accessible.
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.
dbcve · scopedApply the fix and/or workaround provided in HPE Security Bulletin HPESBNS04388, which typically involves updating NetBatch-Plus to the patched version or implementing the documented compensating controls.
Upgrade to Netbatch Plus version t9189h01^abw or t9189l01^aby (or later) as specified in HPE Security Bulletin HPESBNS04388
- Obtain access to HPE Support and the specific Security Bulletin HPESBNS04388 for detailed patch and upgrade instructions
- Identify the current installed version of Nonstop Netbatch Plus
- Consult HPE Security Bulletin HPESBNS04388 to obtain the correct fixed version or patch for your specific version branch
- Apply the recommended fix, which may involve upgrading to t9189h01^abw or t9189l01^aby or later versions
- Verify the fix has been applied by checking the Netbatch Plus version post-remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37931 — 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-2022-37931 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