Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Thermofisher | Torrent Suite | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.414% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Thermofisher torrent Suite Software
|
|
| CPEs | cpe:2.3:a:thermofisher:torrent_suite_software:5.18.1:*:*:*:*:*:*:* | |
| Vendors & Products |
Thermofisher torrent Suite Software
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-1392 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Thermofisher
Thermofisher torrent Suite |
|
| Vendors & Products |
Thermofisher
Thermofisher torrent Suite |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Thermo Fisher Torrent Suite Django application 5.18.1 has weak default credentials, which are stored as fixtures for the Django ORM API. The ionadmin user account can be used to authenticate to default deployments with the password ionadmin. The user guide recommends changing default credentials; however, a password change policy for default administrative accounts is not enforced. Many deployments may retain default credentials, in which case an attacker is likely to be able to successfully authenticate with administrative privileges. | |
| References |
|
|