CVE-2022-46382
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 · uneditedRackN Digital Rebar through 4.6.14, 4.7 through 4.7.22, 4.8 through 4.8.5, 4.9 through 4.9.12, and 4.10 through 4.10.8 has Insecure Permissions. After signing into Digital Rebar, users are issued authentication tokens tied to their account to perform actions within Digital Rebar. During the validation process of these tokens, Digital Rebar did not check if the user account still exists. Deleted Digital Rebar users could still use their tokens to perform actions within Digital Rebar.
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 confidenceRackN Digital Rebar suffers from an authentication bypass vulnerability where deleted users can continue using their existing authentication tokens. The token validation process fails to verify that the associated user account still exists in the system, allowing de-provisioned users to maintain unauthorized access to the platform.
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.6.14>= 4.7, <= 4.7.22>= 4.8, <= 4.8.5>= 4.9, <= 4.9.12>= 4.10, <= 4.10.8CVSS 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 installed Rackn Digital Rebar versionRun 'rebar versions' or check the /opt/rebar directory for version files, or query the API endpoint /api/versionAffected if The installed version falls within any of these ranges: <= 4.6.14, >= 4.7 and <= 4.7.22, >= 4.8 and <= 4.8.5, >= 4.9 and <= 4.9.12, >= 4.10 and <= 4.10.8
-
Review user accounts for deleted or de-provisioned statusQuery the user database or API (GET /api/v3/users) and look for users with a 'deleted', 'deprovisioned', 'disabled', or similar status flag that still have active authentication tokensAffected if There exist users marked as deleted/deprovisioned but their user records or associated tokens remain in the system
-
Examine token validation logicReview the token validation code in the authentication module (typically in auth or token handling middleware) to confirm whether it checks user existence before validating the tokenAffected if The token validation routine does not query the user database to verify the user associated with the token still exists and is active
-
Audit active tokens linked to removed usersQuery the token store or session database for tokens where the owner_id references a user that has been soft-deleted or removed from the active user tableAffected if Tokens exist in the system that are mapped to user IDs that no longer exist in the active user directory
Your environment is affected if you run an affected version AND tokens from deleted/deprovisioned users remain valid because the token validation does not verify user existence.
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 dataImplement user existence verification during token validation and ensure all tokens are revoked when user accounts are deleted. Consider implementing token invalidation mechanisms and regular token expiration policies.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46382 — 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-46382 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