Skip to content

Security: oehrlis/oradba

Security

SECURITY.md

Security Policy

Supported Versions

Security fixes are applied to the latest release only.

Version Supported
Latest
Older

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues.

Report vulnerabilities by email to: stefan.oehrli@oradba.ch

Include in your report:

  • Description of the vulnerability and potential impact
  • Steps to reproduce or proof-of-concept
  • Affected version(s)
  • Any suggested remediation if known

You will receive an acknowledgement within 48 hours and a status update within 7 days indicating whether the report has been accepted or declined.

If accepted, we will coordinate a fix and disclosure timeline with you. We aim to release patches within 30 days of confirmation for critical issues.

Scope

This policy covers the oradba toolset:

  • Shell scripts in src/bin/ and src/lib/
  • The installer (oradba_install.sh) and its build pipeline
  • Configuration defaults shipped with the package

Out of scope:

  • Oracle Database itself — report Oracle product vulnerabilities to Oracle Security
  • Vulnerabilities requiring physical access to the host
  • Issues in third-party tools invoked by oradba (sqlplus, rman, etc.)

Security Design Notes

  • Scripts run with the invoking user's privileges; no setuid/setgid bits
  • No credentials are stored or transmitted by oradba scripts
  • Installer verifies SHA256 checksums for downloaded payload
  • shellcheck linting enforced in CI at -S warning level
  • set -euo pipefail on all executable scripts

There aren’t any published security advisories