Skip to content

Product

Arteche saTECH BCU vulnerabilities

8 published CVES affecting Arteche saTECH BCU, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
8
Critical
0
High
1
Medium
5
Low
2
Unscored
0
CISA KEV
0

Latest Arteche saTECH BCU CVEs

Newest publication first

  1. LowCVSS 2.4 EPSS 0.18%

    SaTECH BCU, in its firmware version 2.1.3, could allow XSS attacks and other malicious resources to be stored on the web server. An attacker with some knowledge of the web application could send a malicious request to the victim users. Through this request, the victims would inte...

  2. MediumCVSS 5.7 EPSS 0.10%

    Cross-site request forgery (CSRF) vulnerability in the web application of saTECH BCU firmware version 2.1.3, which could allow an unauthenticated local attacker to exploit active administrator sessions and perform malicious actions. The malicious actions that can be executed by t...

  3. MediumCVSS 6.9 EPSS 0.22%

    SaTECH BCU, in its firmware version 2.1.3, performs weak password encryption. This allows an attacker with access to the device's system or website to obtain the credentials, as the storage methods used are not strong enough in terms of encryption.

  4. MediumCVSS 6.9 EPSS 0.30%

    SaTECH BCU in its firmware version 2.1.3, allows an authenticated attacker to access information about the credentials that users have within the web (.xml file). In order to exploit this vulnerability, the attacker must know the path, regardless of the user's privileges on the w...

  5. MediumCVSS 6.9 EPSS 0.45%

    An attacker with network access, could capture traffic and obtain user cookies, allowing the attacker to steal the active user session and make changes to the device via web, depending on the privileges obtained by the user.

  6. HighCVSS 8.5 EPSS 0.29%

    Privilege escalation vulnerability in the saTECH BCU firmware version 2.1.3. An attacker with access to the CLI of the device could make use of the nice command to bypass all restrictions and elevate privileges as a superuser.

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.