Files
ARTEX/SECURITY.md
T
BaaRai 9767a70205 docs(security): name the real ingest counters and block rules
in_scope_not_asset counts in-scope events that are not asset types, not
gate rejects: a rejected candidate comes back as an insertion forbidden
error in the insert_assets result. EvaluateAssetGate also applies block
rules whether or not an allow-list exists, so the no-allow-list gap is
about the allow rule, not the whole gate.
2026-11-18 12:12:50 +01:00

5.5 KiB
Raw Blame History

Security Policy

Supported Versions

ARTEX is an autonomous penetration-testing tool. Security fixes are provided only for the latest official release line. The main branch is not considered a stable release and may change at any time.

Only the latest release line receives security fixes. Older releases do not receive fixes; please upgrade to the latest release.

Notes:

  • Please upgrade to the latest release before reporting a vulnerability.
  • Forks, custom builds from arbitrary commits, and modified versions are not covered by official support.

Reporting a Vulnerability

Do not open a public issue for a security vulnerability.

Report through GitHub Security Advisories: Security tab → Report a vulnerability in the BaaRai/ARTEX repository. This is the only reporting channel.

Please include:

  • A description of the vulnerability and its expected impact.
  • The ARTEX version and/or commit hash.
  • Runtime environment (OS, Docker/local, PostgreSQL, LLM provider, etc.).
  • Minimal reproduction steps (PoC).
  • Logs, screenshots, or sample traffic with sensitive data removed.
  • Suggested remediation, if available.

Do not send real third-party data, credentials, tokens, customer data, or unredacted sensitive content.

Scope and Authorized Testing

ARTEX is an offensive-security tool. Test only against:

  • Your own ARTEX deployment in a lab or local environment;
  • Systems you own;
  • Targets explicitly authorized in writing (bug bounty, pentest contract, etc.).

Testing, scanning, or exploiting third-party systems without explicit authorization is strictly prohibited. Reports that violate this principle may be closed without action.

Trusted Inputs and Scope Enforcement

ARTEX trusts the scanner output file (output.json) that ingest_bbot reads. The scope_distance field carried on scope-relevant events is the scanner's own verdict and is ingested as-is: an event the scanner marks in scope (per its own -s/--no-scope configuration) is treated as in scope without being re-checked against ARTEX's rule set.

The enforced trust boundary for asset insertion is insert_assets, which runs every candidate through EvaluateAssetGate: block rules always apply, and a task allow-list is enforced when one is configured. A rejected candidate is returned as an insertion forbidden error for that asset and is never inserted, so it cannot reach task execution. in_scope_not_asset in the ingest_bbot result is a different count: in-scope events that are not asset types (findings and the like).

Accepted gap: when a task has no allow-list, there is no allow rule to apply (block rules still run), and any host carried on an in-scope event that is not blocked enters the graph as an asset. Operators who rely on the scanner's scope rules alone should configure an allow-list per task, or review output.json before feeding it to ARTEX. Cross-checking ingested events against ARTEX's own rule set would change what existing scanner configurations mean for those operators, so it is treated as a deliberate design question (see #317), not an accepted vulnerability.

What to Expect

This is an open-source project maintained on a best-effort basis. We aim to acknowledge a report within about a week and keep you updated, but we cannot guarantee specific response or fix timeframes.

If a Report Is Accepted

  • We will open a private GitHub Security Advisory for coordination.
  • We will identify the release containing the fix when it is published.
  • We may request a CVE if the vulnerability qualifies.
  • We will credit you or your organization in the advisory if you wish.
  • Default disclosure timing: 90 days after a fix is available, or earlier by mutual agreement. If the vulnerability is being exploited in the wild, we may disclose earlier.

If a Report Is Declined

We will explain the reason, for example:

  • It is not a security vulnerability but intended behavior.
  • It is outside ARTEX’s scope (e.g., an issue in an LLM provider, PostgreSQL, Docker, or a browser).
  • There is insufficient information to reproduce it.
  • The report only states that “the tool can be misused” without identifying a specific technical flaw in ARTEX.

Where appropriate, we may convert the report into a public hardening issue or feature request.

Out of Scope

The following are generally not considered ARTEX security vulnerabilities:

  • Attacks or scans against systems you do not own or are not authorized to test.
  • Self-XSS, spam, or brute-force without real impact.
  • Large-scale DoS/DDoS or resource-exhaustion attacks.
  • Social engineering targeting maintainers or users.
  • Issues that exist only in third-party dependencies and do not affect ARTEX.
  • Reports that “ARTEX can be used to attack systems” when the user has valid authorization — this is the nature of a penetration-testing tool, not a vulnerability.
  • Missing headers or hardening configuration without a concrete security impact.

Safe Harbor

We welcome ethical security research. If you follow this policy and test only within authorized scope, we will not pursue legal action against you for good-faith research. This does not exempt you from applicable laws in your jurisdiction.

Disclosure Policy

  • Do not publicly disclose vulnerability details before a fix is available or before the coordinated disclosure period ends.
  • Do not publish a public PoC without maintainer consent.
  • If you do not receive a response within a reasonable time, please ping the contact channel above before disclosing.

Thank you for helping make ARTEX safer.