Known Vulnerabilities for Smart Battery A4 by Gigastone

Listed below are 2 of the newest known vulnerabilities associated with "Smart Battery A4" by "Gigastone".

These CVEs are retrieved based on exact matches on listed software, hardware, and vendor information (CPE data) as well as a keyword search to ensure the newest vulnerabilities with no officially listed software information are still displayed.

Data on known vulnerable versions is also displayed based on information from known CPEs

More device details and information can be found at device.report here: Gigastone Smart Battery A4

Known Vulnerabilities

CVE Shortened Description Severity Publish Date Last Modified
CVE-2019-15069 An unsafe authentication interface was discovered in Smart Battery A4, a multifunctional portable charger, firmware version ?... 9.8 - CRITICAL 2019-09-25 2020-08-24
CVE-2019-15068 A broken access control vulnerability in Smart Battery A4, a multifunctional portable charger, firmware version ?<= r1.7.9 al... 9.8 - CRITICAL 2019-09-25 2023-11-07

Known Affected Configurations (CPE V2.3)

Type Vendor Product Version Update Edition Language
HardwareGigastoneSmart Battery A4-AllAllAll
© CVE.report 2026 |

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

CVE.report and Source URL Uptime Status status.cve.report