Closed ctdfo closed 1 month ago
Hi,
Can you provide me the exact json payload generated by Falco? Did you customize the rule to change the tags or used output fields?
Hi,
Can you provide me the exact json payload generated by Falco? Did you customize the rule to change the tags or used output fields?
Hi @Issif, I am not quite sure what you meant by the exact json generated by Falco
, but this is the Falco log output of the event that replicates the issue:
{"hostname":"aks-default-32511568-vmss000087","output":"14:50:45.460592981: Notice A shell was spawned in a container with an attached terminal (evt_type=execve user=root user_uid=0 user_loginuid=-1 process=sh proc _exepath=/usr/bin/dash parent=runc command=sh terminal=34816 exe_flags=EXE_WRITABLE container_id=9af8a917fc3e container_image=docker.io/falcosecurity/falco-no-driver container_image_tag=0.37.1 container_name=falco k8s_ns=falco k8s_pod_name=falco-44ddf)","priority":"Notice","rule":"Terminal shell in container","source":"syscall","tags":["T1059","container","maturity_stable","mitre_execution","shell"],"time":"2024-04-24T14:50: 45.460592981Z", "output_fields": {"container.id":"9af8a917fc3e","container.image.repository":"docker.io/falcosecurity/falco-no-driver","container.image.tag":"0.37.1","container.name":"falco","evt.arg.flags":"EXE_WR ITABLE","evt.time":1713970245460592981,"evt.type":"execve","k8s.ns.name":"falco","k8s.pod.name":"falco-44ddf","proc.cmdline":"sh","proc.exepath":"/usr/bin/dash","proc.name":"sh","proc.pname":"runc","proc.tty":34816 ,"user.loginuid":-1,"user.name":"root","user.uid":0}}
Please, let me know if this is not what you meant.
This is exactly what I wanted, thanks a lot, it will allow me to try to reproduce. Thanks
The PR #145 fixes that issue, it will be included in the next release. The ETA is before summer.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closing this issue.
Describe the bug We are getting the
interface conversion: interface {} is []string, not string
error in our logs.How to reproduce it Install the Falco Helm chart with Falcosidekick (using version
4.3.0
, which corresponds to app version0.37.1
). Have the UI open at theEvents
section withrefresh
on (I put it at the default of10s
). Then create an event (I opened a shell in one of the running pods to cause theTerminal shell in container
alert). You will notice theinterface conversion: interface {} is []string, not string
in the logs.Expected behaviour No
interface conversion: interface {} is []string, not string
error.Screenshots
Environment
Additional context I am not quite sure where this is coming from. Could it possibly be from the string conversion in the
CountKeyBy
function: