When creating an OPERATOR user account on the BMC, the redfish plugin saved the auto-generated password to /etc/fwupd/redfish.conf without proper restriction, allowing any user on the system to read the same configuration file.
The product makes files or directories accessible to unauthorized actors, even though they should not be.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Fwupd | Fwupd | * | 1.8.5 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | fwupd-0:1.7.8-2.el8 | * |
| Red Hat Enterprise Linux 8.6 Extended Update Support | RedHat | fwupd-0:1.7.4-3.el8_6 | * |
| Red Hat Enterprise Linux 8.8 Extended Update Support | RedHat | fwupd-0:1.7.8-2.el8_8 | * |
| Red Hat Enterprise Linux 9 | RedHat | fwupd-0:1.8.10-2.el9 | * |
| Red Hat Enterprise Linux 9 | RedHat | fwupd-0:1.8.10-2.el9 | * |
| Fwupd | Ubuntu | focal | * |
| Fwupd | Ubuntu | jammy | * |
| Fwupd | Ubuntu | kinetic | * |
| Fwupd | Ubuntu | trusty | * |
| Fwupd | Ubuntu | xenial | * |
Web servers, FTP servers, and similar servers may store a set of files underneath a “root” directory that is accessible to the server’s users. Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any. Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories. In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.