The Historian Channel - 3
Category: Jubilife
Description
The downloaded configuration file contained database schemas as well as information regarding the various alarms in Jubilife’s ICS network. It also contained hardcoded passwords, which could explain how the unauthorized user was eventually able to login successfully.
There is no evidence that this configuration file has been changed in any way, which means the user must have found a different way to modify the alarm logging. However, the configuration file was probably used as part of their information gathering process.
Looking deeper into the suspicious user’s activities, what are the names of the two alarms they deleted from the database?
Flag format: alarm names in ASCII, comma separated (order does not matter). Example: if alarms with names ABCD and EFGH were deleted from database, accepted flags would be ABCD,EFGH or EFGH,ABCD.
Attachments: access.log
Write-up
- Based on the information obtained in The Historian Channel - 1, the last successful login occurred at
04/May/2023:12:22:50
. - Therefore, it is likely that the modification to the alarm logging occurred after that timestamp.
- During our analysis, we discovered several
GET
requests made to/alarms.php
at different time intervals. These requests included query values that resembledSQL DELETE
queries. - Among all the queries, only two of them resulted in a status code of
200
, while the rest returned a status code of500
. - The requests are as follows:
- The first SQL query indicates the name to be the expression
CAST(X'42313237' as TEXT)
which translatesB127
. - The second SQL query indicates the name to be expression
CAST(X'43393639' as TEXT)
which translatesC969
.
Flag: B127,C969