Mass assignment of organization, product and deployment group IDs allows users to write into other organizations and receive their firmware
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| nerves-hub | nerves_hub_web | unaffected |
|
||||||
| nerves-hub | nerves_hub_web | unaffected |
|
||||||
| nerves-hub | nerves_hub_web | unaffected |
|
No data.
No data.
No data available yet.
Vendor Solution
The fixed release's migration takes every device off a deployment group that belongs to a different product and logs each one. Upgrading undoes nothing else done this way. After upgrading, check the database for devices whose organization does not own their product, for signing keys in org_keys whose created_by_id has never been a member of the key's organization, and for certificate authorities whose JITP product belongs to another organization, and remove what you do not recognize. A device moved wholly into another organization, and a product added to one, leave nothing that sets them apart, so review your organization's devices and products as well.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.358% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in the device API, device forms, signing key and product forms and JITP settings in nerves-hub nerves_hub_web allows an authenticated user who manages devices in any organization to write into other organizations via submitted org_id, product_id and deployment_id fields. The device API create and update actions and the dashboard device forms pass the request parameters to NervesHub.Devices.Device.changeset/2, which casts the organization, product, deployment group and update state as given. The signing key and product forms merge the session's organization into the submitted parameters so that a submitted org_id wins, and the JITP changeset accepts any product_id. Each request requires the manage role only in the user's own organization, and any account can create one. A device placed on another organization's deployment group, or moved into its product, is sent that organization's firmware with a download URL. The user cannot change or control devices that already belong to the other organization, and cannot upload firmware to it. This issue affects nerves_hub: from 1.0.0 before 2.5.3. | |
| Title | Mass assignment of organization, product and deployment group IDs allows users to write into other organizations and receive their firmware | |
| First Time appeared |
Nerves-hub
Nerves-hub nerves Hub Web |
|
| Weaknesses | CWE-639 CWE-915 |
|
| CPEs | cpe:2.3:a:nerves-hub:nerves_hub_web:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Nerves-hub
Nerves-hub nerves Hub Web |
|
| References |
|
|
| Metrics |
cvssV4_0
|