Artemis is a modular vulnerability scanner. It's the tool that powers CERT PL scanning activities by checking various aspects of website security and building easy-to-read messages ready to be sent to the scanned organizations.
Quick Start π¨ | Docs π
If you want to use additional modules that weren't included here due to non-BSD-compatible licenses, browse to the Artemis-modules-extra repository.
If you want to modify/develop Artemis, read Development first.
Artemis is experimental software, under active development - use at your own risk.
To chat about Artemis, join the Discord server:
Cooperation and conferences
Artemis was presented at BlackHat USA 2024 in Las Vegas. For more information about Artemis at BlackHat USA click here.
The project was also presented at the 71st TF-CSIRT Meeting in Copenhagen, 69th TF-CSIRT Meeting in Bucharest and the CONFidence conference, among others.
Cooperation
Artemis development was supported by Google Summer of Code 2024.
Features
For an up-to-date list of features, please refer to the documentation. The most important one is the possibility to easily export reports such as:
The following addresses contain version control system data:
Making a code repository public may allow an attacker to learn the inner workings of a system, and if it contains passwords or API keys - also gain unauthorized access. Such data shouldn't be publicly available.
The following addresses contain old Joomla versions:
- https://subdomain2.example.com:443 - Joomla 2.5.4
If a site is no longer used, we recommend shutting it down to eliminate the risk of exploitation of known vulnerabilities in older Joomla versions. Otherwise, we recommend regular Joomla core and plugin updates.
The possibility to automatically prepare such reports enabled us to notify entities in our constituency about hundreds of thousands of vulnerabilities.
Screenshots
Development
To start a locally modified version of Artemis, run:
./scripts/start_devThis script automatically copies the example environment file (env.example) to .env if it doesn't exist. You can then configure the settings in the .env file according to your needs. This includes customizing the user-agent by setting the CUSTOM_USER_AGENT variable, as well as other relevant parameters. For a complete list of configuration variables and their descriptions, please refer to the Configuration section in the documentation.
The Artemis image is then built locally (from the code you are developing) not downloaded from Docker Hub.
For web, you will also be able to see the results of code modifications on the page without reloading the entire container.
Tests
To run the tests, use:
./scripts/testCode formatting
Artemis uses pre-commit to run linters and format the code.
pre-commit is executed on CI to verify that the code is formatted properly.
To run it locally, use:
pre-commit run --all-filesTo set up pre-commit so that it runs before each commit, use:
pre-commit installBuilding the docs
To build the documentation, use:
cd docs
python3 -m venv venv
. venv/bin/activate
pip install -r requirements.txt
make htmlHow do I write my own module?
Please refer to the documentation.
Contributing
Contributions are welcome! We will appreciate both ideas for new Artemis modules (added as GitHub issues) as well as pull requests with new modules or code improvements.
However obvious it may seem we kindly remind you that by contributing to Artemis you agree that the BSD 3-Clause License shall apply to your input automatically, without the need for any additional declarations to be made.
Contributors
Huge thanks to the following people that contributed to Artemis development, especially the KN Cyber science club of Warsaw University of Technology that initiated the project!
