Windows

Fixed a bug where the CPU attack would not affect all processors on systems with more than 64 processors.

Updated dependencies

Updated dependencies

This update fixes Memory attack bugs. Previously, the amount of memory consumed would be limited to RAM. Memory attacks with this update include swap space / all virtual memory.

The Memory attack is more "aggressive" in the sense that the memory allocated by Gremlin during the attack is more difficult to swap to disk.

Updated dependencies.

The Gremlin CLI now has a gremlin check daemon subcommand which reports on the status of any running Gremlin agent.

Updated dependencies.

Updated dependencies.

Updated dependencies.

While never observed, according to the Windows API documentation, getting the current username can fail. If that happened the Gremlin Client would fail to run an attack. Instead, this version resorts to using "unknown" if the username cannot be determined.

Daemon log file management improvements. Previously, the log file was truncated at midnight. That made troubleshooting difficult. The log file is now rolled when it reaches approximately 1 MiB. Ten compressed log files are kept. With this update the current log file typically captures several days and the compressed log files typically capture a few weeks at a modest cost of approximately 2 MiB of disk space.

Fix a bug in Gremlin's argument parsing for the hostnames and ipaddresses arguments for network attacks.

Improve command-line argument parsing by providing better error messages and catching more edge cases related to illegal inputs.

Patch a vulnerability in a 3rd party library that posed a variety of memory corruption scenarios, most likely use-after-free.

Drop invalid targeting tags with a warning.

The daemon version is included in the gremlin check report.

Occasionally the Docker version was incorrectly parsed which would result in the classic driver being used for container attacks.

Some agent API traffic is now consolidated into fewer requests.

Some agent API traffic is now gzip-compressed, reducing network overhead on machines where Gremlin is installed.

Patch a vulnerability in a 3rd party library that posed a potential buffer overflow scenario

Patch a vulnerability in a 3rd party library that posed a potential scenario to operate on dangling memory references

You can now specify the SSL_CERT_FILE variable via the config.yml file. See the advanced configuration page for details on how to use it.

Gremlin now properly interprets escaped newline characters \n for values of the GREMLIN_SSL_CERT environment variable.

Gremlin now reports container and process data at a slower rate, down from every 5 seconds during active attacks (and every 10 seconds otherwise) to every 30 seconds. We've found that this data changes much less frequently than is justified for a 5-10 second interval. This should result in significantly reduced network overhead required to run Gremlin.

Updated dependencies

The Gremlin agent now writes a message to daemon.log when attacks finish. This provides observers of this log with an approximation on when attacks have ended.

Updated dependencies

Gremlin correctly reports Windows 2019 (and later)

Gremlin can be removed if the kernel driver is stopped or removed by hand

Eliminate a nuisance warning that was output at the end of an attack

Updated dependencies

Updated dependencies

Fixed a bug that prevented proper installation on Windows Server 2016

AWS Availability Zone ID (azid) is available for targeting.

AWS tags are now available for targeting.

Fix a regression introduced in 1.0.10 that prevented proper installation on Windows 8.1 / Server 2012 R2

Latency attacks are available

Updated dependencies

On Windows machines with many cores, CPU attack was not utilizing as much CPU time as expected.

Improve error messaging when Gremlin fails to find an IP address for a hostname supplied with the --hostname argument, which can be passed to any network attack. Error message now mentions failures due to specifying a hostname that maps to an invalid DNS record type, such as NS.

Patch a vulnerability in a 3rd party library that posed a potential denial of service to Gremlin's outbound https connections. In practice this is 100% mitigated unless connecting Gremlin through a malicious SSL proxy

Updated dependencies

Add DNS attack

Added more detail to error messages that occur when Gremlin fails to do a DNS lookup of a hostname. Previously the error message did not include the reason for the lookup failure. An example of the new detail we've added is: failed to lookup address information: Name does not resolve.

Fixed a bug where the Gremlin Disk attack would not clean up the impact files it created if it was halted from the UI.

Added additional validity checks on data returned from the Windows API. This improves error handling when the target system does not behave as Gremlin expected.

We now collect an approximate host boot time, this will aid Gremlin to better recognize unique hosts on your team.

Select a default network interface in more cases (also used when Gremlin identifier isn't specified).

Initial release of Gremlin for Windows, allowing attacks to be run on Windows environments. See more about running Gremlin on Windows.