Digital Rebar

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:rackn:digital_rebar:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorRackn (ca1f31a7-b751-503a-b64b-7c0f1c38f65e)
ProductDigital Rebar (4a5d9131-5f09-56f1-bc2b-88c8aa0be33c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-46383 vulnerable 2026-06-08 05:50:38.760482 Details available
RackN 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.
Published: 2022-12-06T00:00:00.000Z
Updated: 2025-04-23T16:13:32.624Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-46382 vulnerable 2026-06-08 05:50:38.759732 Details available
RackN 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.
Published: 2022-12-06T00:00:00.000Z
Updated: 2025-04-23T16:14:39.074Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.