CVE-2023-22644
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 user can reverse engineer the JWT token (JSON Web Token) used in authentication for Manager and API access, forging a valid NeuVector Token to perform malicious activity in NeuVector. This can lead to an RCE.
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 confidenceA JWT authentication bypass vulnerability exists in NeuVector where the JWT token secret used for Manager and API access can be reverse engineered, allowing attackers to forge valid authentication tokens and gain unauthorized access. This token forgery can be leveraged to achieve remote code execution.
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>= 4.2, < 4.2.50-150300.3.66.5>= 4.3, < 4.3.58-150400.3.46.4CVSS 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.
-
Check installed SUSE Manager Server versionRun 'rpm -q susemanager' or check the version through SUSE Manager web UI under Administration > Setup > ProductsAffected if The installed version is >= 4.2 and < 4.2.50-150300.3.66.5, OR >= 4.3 and < 4.3.58-150400.3.46.4
-
Verify NeuVector JWT authentication is in useCheck if the SUSE Manager Server is configured to use NeuVector for authentication by reviewing /etc/rhn/rhn.conf or the authentication settings in the web UI under Administration > Users > AuthenticationAffected if NeuVector authentication module is enabled for Manager or API access
-
Inspect JWT secret configurationExamine the JWT secret file or configuration - typically found in /etc/neuvector/jwt-secret or through SUSE Manager configuration files under /etc/rhn/Affected if The JWT secret is using a default, weak, or known-to-be-reversible secret value rather than a cryptographically strong randomly generated key
-
Check for unauthorized token usageReview authentication logs in /var/log/rhn/rhn_api.log or /var/log/rhn/rhn_web.log for any JWT token validation failures or suspicious authentication patternsAffected if There are signs of token forgery attempts or authentication anomalies that suggest the JWT secret may be compromised
You are affected if your SUSE Manager Server version is within the affected ranges AND NeuVector JWT authentication is enabled, with a weak or potentially compromised JWT secret.
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 · scoped4.2.50-150300.3.66.54.3.58-150400.3.46.4
Rotate all JWT secrets immediately, implement strong and unique secret keys, and upgrade to the patched NeuVector version. Consider implementing token rotation and proper key management practices.
Upgrade to Manager Server 4.2.50-150300.3.66.5 (or later 4.2.x) or 4.3.58-150400.3.46.4 (or later 4.3.x)
- 1. Backup the current Manager Server configuration and database
- 2. Identify the current installed version using 'rpm -q manager-server' or similar
- 3. For SUSE-based systems: run 'zypper patch' or 'zypper update manager-server' to apply the fixed version
- 4. Alternatively, for manual installation: download the fixed version package (4.2.50-150300.3.66.5 for 4.2.x line or 4.3.58-150400.3.46.4 for 4.3.x line)
- 5. Stop the Manager Server service before upgrading
- 6. Install the fixed package using the appropriate package manager command
- 7. Start the Manager Server service after installation
- 8. Verify the installed version matches the fixed release
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-2023-22644 — 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-2023-22644 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