Oracle DBMS
Oracledatabase4 credentials
Database User Password
oracle-dbms / database-user-password
Oracle Database authenticates database users using information in the database itself and supports creating passwords with SQL statements that use the IDENTIFIED BY clause. Oracle documents password protections, profiles, and password management for database users.
Looks like
patternCREATE\s+USER\s+\S+\s+IDENTIFIED\s+BY\s+"?[^";\r\n]+"?ALTER\s+USER\s+\S+\s+IDENTIFIED\s+BY\s+"?[^";\r\n]+"?Location
Oracle data dictionary password verifier state for database users, visible only to privileged users
application config, JDBC URLs, wallet setup files, .env files, and deployment manifests
ORACLE_USER, ORACLE_PASSWORD, TNS_ADMIN, DATABASE_URLOracle Wallet, cloud secret managers, Kubernetes Secrets, and CI/CD variables
application connection strings, SQL scripts, tests, and accidentally committed configs
failed connection traces, JDBC debug logs, SQL*Plus command history, and CI output
tcp/1521Oracle Net listener connection endpoint
Notes
Oracle user passwords are deployment-specific. Do not treat sample users or examples as universal defaults unless a specific image or installer explicitly ships them.
Secure External Password Store Wallet Credential
oracle-dbms / secure-external-password-store
Oracle Secure External Password Store (SEPS) is a client-side wallet used to store password credentials. Oracle documents SEPS as a secure external password store for client-side password credentials.
Location
Oracle Wallet, cwallet.sso, ewallet.p12client-side wallet files containing database connection credentials
sqlnet.ora, tnsnames.oraOracle Net configuration that locates wallets and maps connect descriptors
TNS_ADMIN, ORACLE_HOMEaccidentally committed wallet files, container build contexts, and deployment bundles
VM or container images containing wallet files
Notes
Wallet files can allow passwordless database access from clients that can read the wallet and reach the configured service.
Administrative Password File Credential
oracle-dbms / administrative-password-file
Oracle documents special protections for administrative user passwords, including password files. Administrative users such as SYSDBA can be authenticated by password files, operating system authentication, or other configured methods.
Location
orapw*, PWD*.oraOracle database password file used for administrative authentication
backup stores and infrastructure secrets containing database password files
database server images, backups, and cloned Oracle homes containing password files
database creation logs and administrative scripts that print password file paths or passwords
Notes
Administrative password files are highly sensitive because they can enable privileged SYSDBA-style access depending on server configuration.
Net Service Connection Credential
oracle-dbms / net-service-connection-secret
Oracle Net local naming uses tnsnames.ora to map network service names to connect descriptors. Applications often pair these descriptors with username/password credentials in configuration files or wallets.
Looks like
pattern[A-Za-z0-9_.$#]+/[^\s@]+@[^\s]+Location
tnsnames.ora, sqlnet.oraOracle Net service names and wallet configuration
TNS_ADMIN, ORACLE_CONNECT_STRINGSQL scripts, application configs, deployment scripts, and accidentally committed connect strings
command history, connection errors, and debug traces
Notes
tnsnames.ora usually holds network descriptors rather than passwords, but it is important context for nearby Oracle credentials and wallets.
Scope
Authorized use
LOLCreds helps map the credential surface of real products: known defaults, generated values, credential locations, and exposure patterns.