Pricing Insights
Book a demo
Solutions/By stack

AppSec for PL/SQL

Oracle packages, procedures and triggers are checked together with the rest of the application code.

pkg_report.pkb:31value from the caller
PROCEDURE find(p_name IN VARCHAR2) IS
pkg_report.pkb:36the value goes into the SQL text
v_sql := 'SELECT … WHERE name = ''' || p_name || '''';
pkg_report.pkb:38dynamic SQL
EXECUTE IMMEDIATE v_sql;
SQL injection in dynamic SQL
path provencritical
01PL/SQL

How to load code

Archive or GitLab
Oracle code files: .sql, .pks, .pkb, .trg.
What the platform sees
Packages, procedures, functions, triggers and views, by schema.
Secrets in scripts
Login and password in CONNECT, IDENTIFIED BY, sqlplus strings and EZConnect.
02Rules

What SAST finds in PL/SQL code

  • SQL injection in dynamic SQL
  • Caller's command run with the code owner's privileges
  • OS command from the caller's data
  • Constant encryption key in a DBMS_CRYPTO call
  • Weak hash: MD5, SHA-1, HMAC-MD5
  • Password as an API argument or in DDL text
  • VPD policy disabled from code
  • Audit disabled from code
  • Privilege granted to PUBLIC
  • Excessive system privilege

We will show it on your code

Book a demo