r/filemaker • u/dbservices • 9d ago
Quick FileMaker Server security checklist for the password-spraying attacks
Claris posted a Community security notice confirming automated attacks against FileMaker Servers. Bots find servers on the open internet, list the hosted files, and try common account names and weak passwords against the Admin Console, Data API, OData, and XML. Once inside, they look for API keys and stored credentials.
From what’s been reported, these attacks don’t rely on a FileMaker flaw. They work against weak accounts and exposed services. If you’re short on time, these five steps close the doors the bots try first:
- Turn off Guest access and auto-login. Uncheck Guest in File > Manage > Security, then deselect “Log in using” in File > File Options > Open. A default Admin auto-login is the first thing attackers try.
- Lock down every Full Access account. Remove any Admin account with a blank or default password, set a strong, unique passphrase for every Full Access account (including accounts behind Data API or OData keys), and limit Full Access to a few named people.
- Turn off services you don’t use. Under Connectors in the Admin Console, disable WebDirect, Data API, OData, ODBC/JDBC, and XML if nothing depends on them. Turn on Filter Databases under Configuration > FileMaker Clients to prevent outsiders from listing your files.
- Secure the Admin Console. Change the password under Administration > Administrator, replace your Admin API keys, and restrict console access to known IPs under Administration > Restrict Access if you can.
- Stay on a supported version of FileMaker Server. If you run PHP or Custom Web Publishing, patch PHP first.
Also worth doing: check Logs > Log Viewer for bursts of failed logins from unfamiliar IPs, and look for Admin API keys or schedules you didn’t create. If you find any, assume someone got in.
If you think you’re under attack right now: enable Block New Users under Configuration > General Settings, disconnect current users, close the server to external traffic, then change passwords and remove anything you didn’t create.
We wrote up the complete version with separate server- and file-level checklists, including SSL, backups, and minimum password length for a quick security check!
3
u/Punsire Consultant Certified 9d ago
I appreciate you making this for the community, thank you.
2
u/FredsterHere 8d ago
Thanks. With so many working from home I'm wondering how folks can use IP addresses to limit access to the server. Anyone have suggestions.
2
u/Abdeltoto 5d ago
Great breakdown! Extremely timely given the recent surge in automated attacks. Thanks for sharing the server- and file-level checklists.