CVE-2022-46383
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 exposed a privileged token via a public API endpoint (Incorrect Access Control). The token can be used to escalate privileges within the Digital Rebar system and grant full administrative access.
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 contains an Incorrect Access Control vulnerability where a privileged authentication token is exposed via a publicly accessible API endpoint. This allows unauthenticated attackers to retrieve administrative credentials and gain full system access with full administrative privileges.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Digital Rebar versionRun 'rebar version' command or check the web UI system information page to determine the installed versionAffected if Version is <= 4.6.14, OR between 4.7.0 and 4.7.22, OR between 4.8.0 and 4.8.5, OR between 4.9.0 and 4.9.12, OR between 4.10.0 and 4.10.8
-
Verify API network exposureReview firewall rules, security groups, or network ACLs to check if the Digital Rebar API port is accessible from untrusted IP addresses or the public internetAffected if API port (typically 443 or 3000) is exposed to the internet or untrusted networks without IP restrictions
-
Test for unauthenticated token retrievalSend an unauthenticated HTTP GET request to the API endpoint using a tool like curl or a browser, for example: curl -k https://<your-host>/api/v3/users/1Affected if Request returns privileged authentication tokens, admin credentials, or sensitive user data without requiring authentication
Environment is affected if running an affected version AND the API endpoint is network-accessible, allowing unauthenticated attackers to retrieve administrative tokens.
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 · scopedUpdate Digital Rebar to a version beyond 4.10.8 (or the appropriate patched version for your branch) to remediate the token exposure. Additionally, restrict network access to the API endpoint as an interim control until patching is complete.
Upgrade to 4.10.9 or later (latest stable 4.10.x release), or to the latest release in your current version branch (4.6.15+, 4.7.23+, 4.8.6+, or 4.9.13+)
- Identify the currently running Digital Rebar version using the UI or CLI
- Determine the appropriate upgrade path based on your current version branch (4.6.x, 4.7.x, 4.8.x, 4.9.x, or 4.10.x)
- Review the Digital Rebar upgrade documentation at docs.rackn.io for your version branch
- Back up the Digital Rebar platform configuration and data before upgrading
- Upgrade to the latest stable release in your version branch (4.6.15+, 4.7.23+, 4.8.6+, 4.9.13+, or 4.10.9+)
- Alternatively, upgrade to the latest 4.10.x stable release (4.10.9 or later) which contains the fix
- After upgrade, verify the fix by confirming the privileged token is no longer exposed via public API endpoints
- Rotate any tokens that may have been compromised during the vulnerability window
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46383 — 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-46383 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