Inadequate access control in the Hiperdino REST API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Hiperdino | REST API | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Hiperdino | Rest Api |
|
Vendor Solution
The vulnerability has been resolved by the Dinosol Group's cybersecurity team.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.662% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Inadequate access control in Hiperdino’s REST v1.0 API. The public endpoint ‘customer/check’ could allow an authenticated attacker to enter a telephone number or an email address. When the value entered belongs to a registered customer, the service returns the associated information (email address and telephone number). No authentication is required beyond a static bearer token, and there is no rate limiting or generic error handling. Successful exploitation of this vulnerability could allow a remote attacker to enumerate a user’s contact details, although this would require obtaining a valid static bearer token, constituting an information disclosure vulnerability. | |
| Title | Inadequate access control in the Hiperdino REST API | |
| First Time appeared |
Hiperdino
Hiperdino rest Api |
|
| Weaknesses | CWE-284 | |
| CPEs | cpe:2.3:a:hiperdino:rest_api:1.0:*:*:*:*:*:*:* | |
| Vendors & Products |
Hiperdino
Hiperdino rest Api |
|
| References |
| |
| Metrics |
cvssV4_0
|