CVE-2024-48822: Privilege Escalation in Automatic Systems SlimLane (FtpConfig.php)

An unauthenticated attacker can force-browse to FtpConfig.php on the affected Automatic Systems Maintenance — SlimLane (build 29565) build and both read and overwrite its FTP configuration. Assigned CVE-2024-48822.

CVE ID
CVE-2024-48822
Type
Missing access control / privilege escalation
Affected
Automatic Systems SlimLane (build 29565)
Vector
Unauthenticated, network

Responsible disclosure

This research was carried out by Solusec and published after coordinated disclosure, with a CVE identifier assigned through the appropriate numbering authority. It is shared for defensive and educational purposes so that affected operators can identify and remediate the issue. We do not publish research to enable misuse.

If you operate an affected product and want help confirming or fixing this, get in touch.

Summary

The maintenance interface on the affected Automatic Systems SlimLane build exposes FtpConfig.php without an authorisation check. An unauthenticated attacker able to reach the page can force-browse directly to it and both read and overwrite the device's FTP configuration, as well as invoke the built-in connection-tester functionality.

Because the endpoint trusts the request rather than the session, none of this requires valid credentials. On a pedestrian access gate, control of the FTP settings is a foothold into how the device moves files and where it points.

This vulnerability is tracked as CVE-2024-48822. The authoritative record is on the CVE List (CVE-2024-48822), with severity metrics on the National Vulnerability Database.

Technical detail

The page accepts a JSON body describing the FTP configuration and persists it. A request of the following form updates the stored configuration:

POST /FtpConfig.php HTTP/1.1
Host: <IP>
Content-Length: 106
Accept-Language: en-US,en;q=0.9
User-Agent: Mozilla/5.0
Connection: keep-alive

{"fct":"save_ftp_config","enabled":true,"host":"badhost","user":"myuser","password":"mypass"}

The same page also exposes the current configuration on read, meaning stored credentials can be retrieved, and the tester function can be driven to make the device connect outbound to an attacker-chosen host.

Impact

Unauthenticated read and write of FTP configuration on the device. In practice this allows redirection of file transfers, disclosure of any stored FTP credentials, and abuse of the tester to coerce outbound connections. It is a classic missing access control (broken authorisation) issue: the sensitive function was never gated.

Remediation

  • Enforce authentication and a server-side authorisation check on FtpConfig.php and every other administrative endpoint, rather than relying on the UI not linking to them.
  • Never return stored secrets to the client; treat the FTP password as write-only from the interface.
  • Segment management interfaces off untrusted networks so force-browsing is not reachable in the first place.

Why it matters for operators

Physical access control hardware is frequently deployed on flat networks and rarely retested after installation. A finding like this is only exploitable if the interface is reachable, which is exactly the kind of exposure a network penetration test is designed to catch before somebody else does.

Common questions

What is CVE-2024-48822?

It is a missing-access-control (privilege escalation) issue in the maintenance interface of an Automatic Systems SlimLane build, where FtpConfig.php can be reached without authentication to read and change the device's FTP configuration and use its tester function.

Does exploiting it require credentials?

No. The endpoint does not enforce authorisation, so an attacker who can reach the page over the network can interact with it directly by force-browsing to it.

How do I tell if I am affected?

The research was performed against Automatic Systems Maintenance SlimLane build 29565. If you operate SlimLane pedestrian gates, check with the vendor for a patched build and confirm the maintenance interface is not reachable from user networks. We are happy to help verify this on an authorised basis.

How was this disclosed?

Through coordinated disclosure with a CVE assigned by the relevant numbering authority. The write-up is published for defensive purposes.

Related

Found a vulnerability, or need testing that finds them?

We run coordinated disclosure for our own research and help vendors triage and fix what we report. If you need testing to this standard, the scoping conversation is free.