Event ID 11 - Empty TargetFilename
@MarioHewardt ci sta già lavorando.
Dal 23/10/2023.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Describe the bug
All events ID 11 - File Create are missing values in TargetFilename field. Only dash (-) is being shown.
Works OK for event ID 23 - File Delete - path and filename is present.
To Reproduce
Happened with both default config ("catch all" and custom configs)
Sysmon version
Tested on both 1.3.0 and newest 1.3.1
Distro/kernel version
Linux xxx 5.4.0-72-generic #80-Ubuntu SMP Mon Apr 12 17:35:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 20.04LTS
Sysmon configuration
Tested with default catch all config. Tested this one: https://github.com/microsoft/MSTIC-Sysmon/blob/main/linux/configs/main.xml and tested couple of custom configurations, all with same results - events are being collected but TargetFilename field is empty.
Logs
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:58:58.151
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:58:58.151
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:58:58.151
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:58:58.151
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:58:58.151
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:58:58.151
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:09.978
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:09.978
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:14.168
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:14.168
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:14.168
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:14.168
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:14.168
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:14.168
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:21.021
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:21.021
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:21.030
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:21.030
User: -
Expected behavior
A path and file name is expected in TargetFilename same way as for ID 23 file delete. Without this information it is not possible to investigate events and perform filtering in config file.
Thank you.
Regards,
Jozef
- Lingua principale
- C
- Stelle
- 2.2k
- Fork
- 222
- Merge medio
- 4h 50m
- PR unite (30g)
- 3
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/Sysmon-Linux
-
ProcessCreate: ParentImage is empty when the parent starts the process from a non-main threadAperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
microsoft/Sysmon-Linux#253 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
microsoft/Sysmon-Linux#252 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
microsoft/Sysmon-Linux#247 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 12/100
microsoft/Sysmon-Linux#246 · 3 commenti ·
-
Sysmon service executable remains `(deleted)` after restart, causing repeated needrestart restarts and systemd start-limit-hitForse di nuovo libera @MarioHewardt l’ha presa 31 giorni fa e non c’è nessuna pull request aperta. Aperta
microsoft/Sysmon-Linux#244 · 1 assegnatario ·
Tutte le issue di microsoft/Sysmon-Linux
Issue simili
-
enhancement good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
bug multiplayer status: planned
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
ChupathingyCE/chupathingyce#851 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
HigherOrderCO/Bend#2104 ·
-
research-radar
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
good first issue help wanted program
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
hffgzktbcc-blip/ounce-core#297 ·
I maintainer di solito rispondono entro 1 giorno