databasement vulnerabilities

A vulnerability was found in David-Crty databasement up to 1.7.1, affecting the database-servers API endpoint in app/Http/Requests/Api/V1/RestoreRequest.php. Manipulation of the schema_name argument results in path traversal. The attack can be launched remotely but requires high complexity and is difficult to exploit; the exploit has been made public.

The Databasement application (up to version 1.8.1) has a Missing Authorization vulnerability in the Scheduled Restore component, in the file app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php, due to manipulation of the schema_name argument. The attack can be executed remotely, and the exploit has been publicly disclosed.

databasement before 1.8.2 allows remote code execution because it runs certain commands (e.g., mariadb-dump) with a database name that can be specified by any authenticated user. For example, --result-file=/app/public/index.php can write to index.php. In other words, quoting prevents OS command injection in mariadb-dump, but the argument injection alone is sufficient for code execution indirectly.

A vulnerability was determined in David-Crty databasement up to 1.7.1. Affected is the SnapshotPolicy.viewAny/SnapshotPolicy.view function of the /api/v1/snapshots file in the Snapshot Model component. This manipulation causes improper access controls. Remote exploitation is possible. The exploit has been publicly disclosed. Upgrading to version 1.7.2 addresses the issue.

Databasement before 1.7.14 validates invitation tokens only when the acceptance page loads, caching the authorization decision without re-checking token validity during acceptance. Attackers with a leaked or forwarded invitation link can load the page while pending, then accept the invitation after the legitimate user has already accepted it to overwrite the account password and gain authenticated access to managed database credentials and secrets.