HomeBox: API keys are not revoked on password change and never expire by default, so a leaked key survives full credential rotation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sysadminsmedia | homebox | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Sysadminsmedia | Homebox |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sysadminsmedia
Sysadminsmedia homebox |
|
| Vendors & Products |
Sysadminsmedia
Sysadminsmedia homebox |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | HomeBox is a home inventory and organization system. Prior to 0.27.0, a HomeBox password change revokes the user's other session tokens but does not revoke the user's API keys, and API keys have no default API-key expiration. An attacker who has obtained an API key can therefore retain full API-level access after the account owner changes the password and can keep that access indefinitely unless the owner discovers and manually deletes the key by ID. Because the password change terminates other sessions, the surviving API credential can evade the owner's expected containment and detection. This issue is fixed in version 0.27.0. | |
| Title | HomeBox: API keys are not revoked on password change and never expire by default, so a leaked key survives full credential rotation | |
| Weaknesses | CWE-1188 CWE-613 |
|
| References |
| |
| Metrics |
cvssV3_1
|