The FACSChorus software database can be accessed directly with the privileges of the currently logged-in user. A threat actor with physical access could potentially gain credentials, which could be used to alter or destroy data stored in the database.
Weakness
A product defines a set of insecure permissions that are inherited by objects that are created by the program.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Facschorus |
Bd |
5.0 (including) |
5.0 (including) |
| Facschorus |
Bd |
5.1 (including) |
5.1 (including) |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References