Vendor
9 published CVES affecting piigab, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
Newest publication first
PiiGAB M-Bus is vulnerable to cross-site request forgery. An attacker who wants to execute a certain command could send a phishing mail to the owner of the device and hope that the owner clicks on the link. If the owner of the device has a cookie stored that allows the owner to b...
PiiGAB M-Bus stores passwords using a weak hash algorithm.
There are no requirements for setting a complex password for PiiGAB M-Bus, which could contribute to a successful brute force attack if the password is inline with recommended password guidelines.
PiiGAB M-Bus does not validate identification strings before processing, which could make it vulnerable to cross-site scripting attacks.
PiiGAB M-Bus stores credentials in a plaintext file, which could allow a low-level user to gain admin credentials.
PiiGAB M-Bus contains hard-coded credentials which it uses for authentication.
PiiGAB M-Bus transmits credentials in plaintext format.
The number of login attempts is not limited. This could allow an attacker to perform a brute force on HTTP basic authentication.
PiiGAB M-Bus SoftwarePack 900S does not correctly sanitize user input, which could allow an attacker to inject arbitrary commands.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.