{"vulnerability": "CVE-2020-2023", "sightings": [{"uuid": "daa0ddad-9a30-4c80-a71e-abd8577a06a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "published-proof-of-concept", "source": "https://t.me/CVEhub/12430", "content": "\ud83d\udc7eKEYWORD SERVICE \ud83c\udff7#CVE-2023\nName: *kata-cve-2020-2023-poc*\nGithub: https://github.com/ssst0n3/kata-cve-2020-2023-poc", "creation_timestamp": "2026-07-31T00:00:06.093729Z"}, {"uuid": "e1a8f57b-1548-42c0-b409-e51ec2f8cff0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/CVEhub/12430", "content": "\ud83d\udc7eKEYWORD SERVICE \ud83c\udff7#CVE-2023\nName: *kata-cve-2020-2023-poc*\nGithub: https://github.com/ssst0n3/kata-cve-2020-2023-poc", "creation_timestamp": "2026-07-29T12:00:33.309338Z"}, {"uuid": "b74d1a6d-b776-4553-b555-bcdf69b1d5bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/CVEhub/12430", "content": "\ud83d\udc7eKEYWORD SERVICE \ud83c\udff7#CVE-2023\nName: *kata-cve-2020-2023-poc*\nGithub: https://github.com/ssst0n3/kata-cve-2020-2023-poc", "creation_timestamp": "2026-07-30T00:00:58.044688Z"}, {"uuid": "fb4c3a9f-cd97-4e9c-8213-788e3ebabe8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/hacking_Attack/11444", "content": "container_escape  7.8 (https://nvd.nist.gov/vuln/detail/CVE-2016-5195)  \u2705      cve-2018-18955 (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/kernel/cve-2018-18955.yaml)  kernel  privilege_escalation  7.0 (https://nvd.nist.gov/vuln/detail/CVE-2018-18955)  \u2705      cve-2020-14386 (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/kernel/cve-2020-14386.yaml)  kernel  container_escape  7.8 (https://nvd.nist.gov/vuln/detail/CVE-2020-14386)  \u2705      cap_dac_read_search-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/cap_dac_read_search-container.yaml)  config  container_escape  -  \u2705      cap_sys_admin-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/cap_sys_admin-container.yaml)  config  container_escape  -  \u2705      cap_sys_ptrace-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/cap_sys_ptrace-container.yaml)  config  container_escape  -  \u2705      privileged-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/privileged-container.yaml)  config  container_escape  -  \u2705      mount-docker-sock (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/mounts/mount-docker-sock.yaml)  mount  container_escape  -  \u2705      mount-host-etc (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/mounts/mount-host-etc.yaml)  mount  container_escape  -  \u2705      mount-host-procfs (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/mounts/mount-host-procfs.yaml)  mount  container_escape  -  \u2705      kata-escape-2020 (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/kata-containers/kata-escape-2020.yaml)  kata-containers  container_escape  6.3 (https://nvd.nist.gov/vuln/detail/CVE-2020-2023)/8.8 (https://nvd.nist.gov/vuln/detail/CVE-2020-2025)/8.8 (https://nvd.nist.gov/vuln/detail/CVE-2020-2026)  \u2705      \n4.2 Vulnerable Scenes Related to Cloud Native Applications\n  These scenes are mainly derived from other open-source projects:    Vulhub (https://github.com/vulhub/vulhub)  DVWA (https://github.com/digininja/DVWA)    We express sincere gratitude to projects above!  Metarget converts scenes in projects above to Deployments and Services resources in Kubernetes (thanks to kompose (https://github.com/kubernetes/kompose)).  To list vulnerable scenes related to cloud native applications supported by Metarget, just run\uff1a  ./metarget appv list  \n5 DEMO", "creation_timestamp": "2026-09-01T20:02:38.794380Z"}, {"uuid": "8d364a60-6e2b-47bb-b7da-376e5374d4bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/hacking_Attack/11442", "content": "2.2 Manage Cloud Native (https://www.kitploit.com/search/label/Cloud%20Native) Components\n  usage: metarget gadget [-h] subcommand ...\n\npositional arguments:\n  subcommand  description\n    list      list supported gadgets\n    install   install gadgets\n    remove    uninstall gadgets\n\noptional arguments:\n  -h, --help  show this help message and exit\n  \n2.2.1 Case: Install Docker with Specified Version\n  Run:  ./metarget gadget install docker --version 18.03.1  If the command above completes successfully, 18.03.1 Docker will be installed.  \n2.2.2 Case: Install Kubernetes with Specified Version\n  Run:  ./metarget gadget install k8s --version 1.16.5  If the command above completes successfully, 1.16.5 Kubernetes single-node cluster will be installed.  Note:  Usually, lots of options need to be configured in Kubernetes. As a security research project, Metarget provides some options for installation of Kubernetes:    -v VERSION, --version VERSION\n                        gadget version\n  --cni-plugin CNI_PLUGIN\n                        cni plugin, flannel by default\n  --pod-network-cidr POD_NETWORK_CIDR\n                        pod network cidr, default cidr for each plugin by\n                        default\n  --taint-master        taint master node or not\n  Metarget supports deployment of multi-node cluster. If you want to add more nodes into the cluster, you can copy tools/install_k8s_worker.sh script and run it on each worker nodes after the successful installation of single-node cluster.  \n2.2.3 Case: Install Kata-containers with Specified Version\n  Run:  ./metarget gadget install kata --version 1.10.0  If the command above completes successfully, 1.10.0 Kata-containers will be installed.  Note:  You can also specify the type of kata runtime (qemu/clh/fc/...) with --kata-runtime-type option, which is qemu by default.  \n2.2.4 Case: Install Linux Kernel (https://www.kitploit.com/search/label/Linux%20Kernel) with Specified Version\n  Run:  ./metarget gadget install kernel --version 5.7.5  If the command above completes successfully, 5.7.5 kernel will be installed.  Note:  Currently, Metarget install kernels in 2 ways:    apt  if apt package is not available, download *.deb remotely from Ubuntu and try to install    After successful installation of kernel, reboot of system is needed. Metarget will prompt to reboot automatically.  \n2.3 Manage Vulnerable Scenes Related to Cloud Native Components\n  usage: metarget cnv [-h] subcommand ...\n\npositional arguments:\n  subcommand  description\n    list      list supported cloud native vulnerabilities\n    install   install cloud native vulnerabilities\n    remove    uninstall cloud native vulnerabilities\n\noptional arguments:\n  -h, --help  show this help message and exit\n  Run ./metarget cnv list to see vulnerable scenes related to cloud native components supported currently.  \n2.3.1 Case: CVE-2019-5736\n  Run:  ./metarget cnv install cve-2019-5736  If the command above completes successfully, Docker with CVE-2019-5736 will be installed\u3002  \n2.3.2 Case: CVE-2018-1002105\n  Run:  ./metarget cnv install cve-2018-1002105  If the command above completes successfully, Kubernetes with CVE-2018-1002105 will be installed\u3002  \n2.3.3 Case: Kata-containers Escape\n  Run:  ./metarget cnv install kata-escape-2020  If the command above completes successfully, Kata-containers with CVE-2020-2023/2025/2026 will be installed\u3002  \n2.3.4 Case: CVE-2016-5195\n  Run:  ./metarget cnv install cve-2016-5195  If the command above completes successfully, kernel with CVE-2016-5195 will be installed\u3002  \n2.4 Manage Vulnerable Scenes Related to Cloud Native Applications\n  usage: metarget appv [-h] subcommand ...\n\npositional arguments:\n  subcommand  description\n    list      list supported application vulnerabilities\n    install   install application vulnerabilities\n    remove    uninstall application vulnerabilities\n\noptional arguments:\n  -h, --help  show this help message and exit", "creation_timestamp": "2026-09-01T20:02:39.758456Z"}, {"uuid": "2a9e76df-441f-4eef-9d7e-50dcfd775a3a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/hacking_Attack/11441", "content": "1 Introduction\n  Metarget = meta- + target, a framework providing automatic constructions of vulnerable infrastructures, used to deploy simple or complicated vulnerable cloud native targets swiftly and automatically.  \n1.1 Why Metarget?\n  During security researches, we might find that the deployment of vulnerable environment often takes much time, while the time spent on testing PoC or ExP is comparatively short. In the field of cloud native security, thanks to the complexity of cloud native systems, this issue is more terrible.  There are already some excellent security projects like Vulhub (https://github.com/vulhub/vulhub), VulApps (https://github.com/Medicean/VulApps) in the open-source community, which pack vulnerable scenes into container images, so that researchers could utilize them and deploy scenes quickly.  However, these projects mainly focus on vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) in applications. What if we need to study the vulnerabilities in the infrastructures like Docker, Kubernetes and even Linux kernel?  Hence, we develop Metarget and hope to solve the deployment issue above to some extent. Furthermore, we also expect that Metarget could help to construct multilayer vulnerable cloud native scenes automatically.  \n1.2 Install Vulnerability!\n  In this project, we come up with concepts like installing vulnerabilities and installing vulnerable scenes. Why not install vulnerabilities just like installing softwares? We can do that, because our goals are security research and offensive security.  To be exact, we expect that:    metarget cnv install cve-2019-5736 will install Docker with CVE-2019-5736 onto the server.  metarget cnv install cve-2018-1002105 will install Kubernetes with CVE-2018-1002105 onto the server.  metarget cnv install kata-escape-2020 will install Kata-containers with CVE-2020-2023/2025/2026 onto the server.  metarget cnv install cve-2016-5195 will install a kernel with DirtyCoW into the server.    It's cool, right? No more steps. No RTFM. Execute one command and enjoy your coffee.  Furthermore, we expect that:    with Metarget's help, ethical hackers are able to deploy simple or complicated cloud native targets swiftly and learn by hacking cloud native environments.  metarget appv install dvwa will install a DVWA (https://github.com/digininja/DVWA) target onto our vulnerable infrastructure.  metarget appv install thinkphp-5-0-23-rce --external will install a ThinkPHP RCE vulnerability (https://www.kitploit.com/search/label/Vulnerability) with NodePort service onto our vulnerable infrastructure.    You can just run 5 commands below after installing a new Ubuntu and obtain a multi-layer vulnerable scene:  ./metarget cnv install cve-2016-5195 # container escape with dirtyCoW\n./metarget cnv install cve-2019-5736 # container escape with docker\n./metarget cnv install cve-2018-1002105 # kubernetes single-node cluster with cve-2018-1002105\n./metarget cnv install privileged-container # deploy a privileged container\n./metarget appv install dvwa --external # deploy dvwa target  RCE, container escape, lateral movement, persistence, they are yours now.  More awesome functions are coming! Stay tuned :)  Note:  Thie project aims to provide vulnerable scenes for security research. The security of scenes generated is not guaranteed. It is NOT recommended to deploy components or scenes with Metarget on the Internet.  \n2 Usage\n  \n2.1 Basic Usage\n  usage: metarget [-h] [-v] subcommand ...\n\nautomatic constructions of vulnerable infrastructures\n\npositional arguments:\n  subcommand     description\n    gadget       cloud native gadgets (docker/k8s/...) management\n    cnv          cloud native vulnerabilities management\n    appv         application vulnerabilities management\n\noptional arguments:\n  -h, --help     show this help message and exit\n  -v, --version  show program's version number and exit\n  Run ./metarget gadget list to see cloud native components supported currently.", "creation_timestamp": "2026-09-01T20:02:40.017853Z"}, {"uuid": "5eab7c36-5144-4615-ba9a-2302553f669e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/hacking_Attack/11441", "content": "1 Introduction\n  Metarget = meta- + target, a framework providing automatic constructions of vulnerable infrastructures, used to deploy simple or complicated vulnerable cloud native targets swiftly and automatically.  \n1.1 Why Metarget?\n  During security researches, we might find that the deployment of vulnerable environment often takes much time, while the time spent on testing PoC or ExP is comparatively short. In the field of cloud native security, thanks to the complexity of cloud native systems, this issue is more terrible.  There are already some excellent security projects like Vulhub (https://github.com/vulhub/vulhub), VulApps (https://github.com/Medicean/VulApps) in the open-source community, which pack vulnerable scenes into container images, so that researchers could utilize them and deploy scenes quickly.  However, these projects mainly focus on vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) in applications. What if we need to study the vulnerabilities in the infrastructures like Docker, Kubernetes and even Linux kernel?  Hence, we develop Metarget and hope to solve the deployment issue above to some extent. Furthermore, we also expect that Metarget could help to construct multilayer vulnerable cloud native scenes automatically.  \n1.2 Install Vulnerability!\n  In this project, we come up with concepts like installing vulnerabilities and installing vulnerable scenes. Why not install vulnerabilities just like installing softwares? We can do that, because our goals are security research and offensive security.  To be exact, we expect that:    metarget cnv install cve-2019-5736 will install Docker with CVE-2019-5736 onto the server.  metarget cnv install cve-2018-1002105 will install Kubernetes with CVE-2018-1002105 onto the server.  metarget cnv install kata-escape-2020 will install Kata-containers with CVE-2020-2023/2025/2026 onto the server.  metarget cnv install cve-2016-5195 will install a kernel with DirtyCoW into the server.    It's cool, right? No more steps. No RTFM. Execute one command and enjoy your coffee.  Furthermore, we expect that:    with Metarget's help, ethical hackers are able to deploy simple or complicated cloud native targets swiftly and learn by hacking cloud native environments.  metarget appv install dvwa will install a DVWA (https://github.com/digininja/DVWA) target onto our vulnerable infrastructure.  metarget appv install thinkphp-5-0-23-rce --external will install a ThinkPHP RCE vulnerability (https://www.kitploit.com/search/label/Vulnerability) with NodePort service onto our vulnerable infrastructure.    You can just run 5 commands below after installing a new Ubuntu and obtain a multi-layer vulnerable scene:  ./metarget cnv install cve-2016-5195 # container escape with dirtyCoW\n./metarget cnv install cve-2019-5736 # container escape with docker\n./metarget cnv install cve-2018-1002105 # kubernetes single-node cluster with cve-2018-1002105\n./metarget cnv install privileged-container # deploy a privileged container\n./metarget appv install dvwa --external # deploy dvwa target  RCE, container escape, lateral movement, persistence, they are yours now.  More awesome functions are coming! Stay tuned :)  Note:  Thie project aims to provide vulnerable scenes for security research. The security of scenes generated is not guaranteed. It is NOT recommended to deploy components or scenes with Metarget on the Internet.  \n2 Usage\n  \n2.1 Basic Usage\n  usage: metarget [-h] [-v] subcommand ...\n\nautomatic constructions of vulnerable infrastructures\n\npositional arguments:\n  subcommand     description\n    gadget       cloud native gadgets (docker/k8s/...) management\n    cnv          cloud native vulnerabilities management\n    appv         application vulnerabilities management\n\noptional arguments:\n  -h, --help     show this help message and exit\n  -v, --version  show program's version number and exit\n  Run ./metarget gadget list to see cloud native components supported currently.", "creation_timestamp": "2026-09-02T01:03:16.683038Z"}, {"uuid": "53aeb933-04f8-451c-b4d2-f0aa39d7d1a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/hacking_Attack/11444", "content": "container_escape  7.8 (https://nvd.nist.gov/vuln/detail/CVE-2016-5195)  \u2705      cve-2018-18955 (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/kernel/cve-2018-18955.yaml)  kernel  privilege_escalation  7.0 (https://nvd.nist.gov/vuln/detail/CVE-2018-18955)  \u2705      cve-2020-14386 (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/kernel/cve-2020-14386.yaml)  kernel  container_escape  7.8 (https://nvd.nist.gov/vuln/detail/CVE-2020-14386)  \u2705      cap_dac_read_search-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/cap_dac_read_search-container.yaml)  config  container_escape  -  \u2705      cap_sys_admin-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/cap_sys_admin-container.yaml)  config  container_escape  -  \u2705      cap_sys_ptrace-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/cap_sys_ptrace-container.yaml)  config  container_escape  -  \u2705      privileged-container (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/configs/privileged-container.yaml)  config  container_escape  -  \u2705      mount-docker-sock (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/mounts/mount-docker-sock.yaml)  mount  container_escape  -  \u2705      mount-host-etc (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/mounts/mount-host-etc.yaml)  mount  container_escape  -  \u2705      mount-host-procfs (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/mounts/mount-host-procfs.yaml)  mount  container_escape  -  \u2705      kata-escape-2020 (https://github.com/brant-ruan/metarget/blob/master/vulns_cn/kata-containers/kata-escape-2020.yaml)  kata-containers  container_escape  6.3 (https://nvd.nist.gov/vuln/detail/CVE-2020-2023)/8.8 (https://nvd.nist.gov/vuln/detail/CVE-2020-2025)/8.8 (https://nvd.nist.gov/vuln/detail/CVE-2020-2026)  \u2705      \n4.2 Vulnerable Scenes Related to Cloud Native Applications\n  These scenes are mainly derived from other open-source projects:    Vulhub (https://github.com/vulhub/vulhub)  DVWA (https://github.com/digininja/DVWA)    We express sincere gratitude to projects above!  Metarget converts scenes in projects above to Deployments and Services resources in Kubernetes (thanks to kompose (https://github.com/kubernetes/kompose)).  To list vulnerable scenes related to cloud native applications supported by Metarget, just run\uff1a  ./metarget appv list  \n5 DEMO", "creation_timestamp": "2026-09-02T01:03:14.496064Z"}, {"uuid": "4b5bb9d1-a70a-4948-8330-3baf03d73289", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-2023", "type": "seen", "source": "https://t.me/hacking_Attack/11442", "content": "2.2 Manage Cloud Native (https://www.kitploit.com/search/label/Cloud%20Native) Components\n  usage: metarget gadget [-h] subcommand ...\n\npositional arguments:\n  subcommand  description\n    list      list supported gadgets\n    install   install gadgets\n    remove    uninstall gadgets\n\noptional arguments:\n  -h, --help  show this help message and exit\n  \n2.2.1 Case: Install Docker with Specified Version\n  Run:  ./metarget gadget install docker --version 18.03.1  If the command above completes successfully, 18.03.1 Docker will be installed.  \n2.2.2 Case: Install Kubernetes with Specified Version\n  Run:  ./metarget gadget install k8s --version 1.16.5  If the command above completes successfully, 1.16.5 Kubernetes single-node cluster will be installed.  Note:  Usually, lots of options need to be configured in Kubernetes. As a security research project, Metarget provides some options for installation of Kubernetes:    -v VERSION, --version VERSION\n                        gadget version\n  --cni-plugin CNI_PLUGIN\n                        cni plugin, flannel by default\n  --pod-network-cidr POD_NETWORK_CIDR\n                        pod network cidr, default cidr for each plugin by\n                        default\n  --taint-master        taint master node or not\n  Metarget supports deployment of multi-node cluster. If you want to add more nodes into the cluster, you can copy tools/install_k8s_worker.sh script and run it on each worker nodes after the successful installation of single-node cluster.  \n2.2.3 Case: Install Kata-containers with Specified Version\n  Run:  ./metarget gadget install kata --version 1.10.0  If the command above completes successfully, 1.10.0 Kata-containers will be installed.  Note:  You can also specify the type of kata runtime (qemu/clh/fc/...) with --kata-runtime-type option, which is qemu by default.  \n2.2.4 Case: Install Linux Kernel (https://www.kitploit.com/search/label/Linux%20Kernel) with Specified Version\n  Run:  ./metarget gadget install kernel --version 5.7.5  If the command above completes successfully, 5.7.5 kernel will be installed.  Note:  Currently, Metarget install kernels in 2 ways:    apt  if apt package is not available, download *.deb remotely from Ubuntu and try to install    After successful installation of kernel, reboot of system is needed. Metarget will prompt to reboot automatically.  \n2.3 Manage Vulnerable Scenes Related to Cloud Native Components\n  usage: metarget cnv [-h] subcommand ...\n\npositional arguments:\n  subcommand  description\n    list      list supported cloud native vulnerabilities\n    install   install cloud native vulnerabilities\n    remove    uninstall cloud native vulnerabilities\n\noptional arguments:\n  -h, --help  show this help message and exit\n  Run ./metarget cnv list to see vulnerable scenes related to cloud native components supported currently.  \n2.3.1 Case: CVE-2019-5736\n  Run:  ./metarget cnv install cve-2019-5736  If the command above completes successfully, Docker with CVE-2019-5736 will be installed\u3002  \n2.3.2 Case: CVE-2018-1002105\n  Run:  ./metarget cnv install cve-2018-1002105  If the command above completes successfully, Kubernetes with CVE-2018-1002105 will be installed\u3002  \n2.3.3 Case: Kata-containers Escape\n  Run:  ./metarget cnv install kata-escape-2020  If the command above completes successfully, Kata-containers with CVE-2020-2023/2025/2026 will be installed\u3002  \n2.3.4 Case: CVE-2016-5195\n  Run:  ./metarget cnv install cve-2016-5195  If the command above completes successfully, kernel with CVE-2016-5195 will be installed\u3002  \n2.4 Manage Vulnerable Scenes Related to Cloud Native Applications\n  usage: metarget appv [-h] subcommand ...\n\npositional arguments:\n  subcommand  description\n    list      list supported application vulnerabilities\n    install   install application vulnerabilities\n    remove    uninstall application vulnerabilities\n\noptional arguments:\n  -h, --help  show this help message and exit", "creation_timestamp": "2026-09-02T01:03:15.468983Z"}]}