PAGES
← all tools
◆ Exploitation & C2

odat

2.2.0 open-source

Penetration testing tool for remotely testing Oracle Database security, including SID/credential discovery, privilege escalationprivilege escalationGaining permissions beyond those an account or process initially had. It can turn limited access into administrator control or access to another user's resources., and OS command execution.

source ↗ rss ↗ What is a cyber toolchain?

Summary

odat is an open-source command-line tool that tests Oracle Databases for exploitable weaknesses remotely, and it is free to use. It covers the full attack pathattack pathA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately.: discovering valid SIDs and credentials on a listening database, escalating a low-privilege account to DBA or SYSDBA, and using that access to run system commands, including reverse shells, on the host. It runs against Oracle 10g through 19c, taking targets individually or in bulk from nmap XML output or a plain host list, which suits red teamers and penetration testers working through database infrastructure rather than developers securing application code. It sits in the exploitation-tooling space alongside other protocol-specific attack tools rather than general vulnerability scanners. First committed in 2014 and still active, with 11 contributors and 15 commits in the past year.

Penetration testing tool for remotely testing Oracle Database security, including SID/credential discovery, privilege escalation, and OS command execution.

How odat helps

Which valid SIDs and service names exist on an Oracle listener I've found?

probes the listener directly and enumerates the SIDs and service names it accepts, without needing credentials first

Which credentials will actually authenticate against this database?

runs credential checks across accounts and returns the ones that succeed, working from a single target or a whole list at once

Can this low-privilege Oracle account be escalated to DBA or SYSDBA?

drives known privilege-escalation paths against the supplied account and reports whether elevated access is reachable from it

What can I do on the host once I have database access?

uses the authenticated session to run system commands or push a reverse shell, turning database access into host-level access

Which hosts in a scanned network segment are exposed Oracle listeners worth attacking?

reads nmap XML output or a plain host list and runs the same SID, credential and access checks across every target in bulk

Does the version of Oracle I'm facing change what's exploitable?

runs the same modules against 10g through 19c, so the same test set applies regardless of which version is listening

all 3 features, with the evidence for each →

Languages

Not documented

Features

3 capabilities · 2 backed by code, an API document or a real run

Built from odat's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What odat offers you

  • Command-line interface2
All capabilities 3 capabilities
Service name discovery verified Provides a helper (snguesser) to identify valid service names for use with the tool. 2 other sources · first seen Mar 2021

command line

example

  • Show ODAT help menu ./odat.py -h
Oracle Database penetration testing shipped Provides capabilities for remotely testing Oracle Database security, including SID and credential discovery, privilege escalation, and OS command execution. 1 release · 1 other source · first seen Apr 2016

Also counts toward: Command-line interface

release

  • Adds the tnspoison command to exploit TNS listener poisoning (CVE-2012-1675 + CVE-2012-3137) 2.2.0 · Apr 2016 · source · release history

docs

  • Penetration testing tool for remotely testing Oracle Database security, including SID/credential discovery, privilege escalation, and OS command execution.
Host list input from file verified Accepts a file containing one host per line (in 'ip:port' or 'ip' format) as input for scanning targets. 1 other source · first seen Mar 2021

Also counts toward: Command-line interface

command line

  • -l — filename which contains hosts (one ip on each line: "ip:port" or "ip" only) 5.1 · Mar 2021 · command-line history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for odat, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail odat puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

1 entry

  1. April 20161

    1 entry

    1. 2.2.0 Apr 22, 2016 · release notes

      ODAT 2.2.0 adds tnspoison module and multi-file auth for remote attacks

      └──▷ GET THIS VERSION 
      $ git clone --branch 2.2.0 https://github.com/quentinhardy/odat.git
# already have the repo? check out this version:
$ git checkout 2.2.0
      • Adds the tnspoison command to exploit TNS listener poisoning (CVE-2012-1675 + CVE-2012-3137)

      1 detail in Everything

    Project health

    Issue, contributor and maintainer activity in quentinhardy/odat, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 1 +1 vs prior 12 months
    2. Maintainers 1 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close 2.5 years issues closed, last 12 months
    6. Open backlog 1 of 49 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 1
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,778
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback