fix(oceanbase-oracle): escape SQL identifiers and literals in metadata/DDL paths (#1914)#2205
Open
HandSonic wants to merge 4 commits into
Open
fix(oceanbase-oracle): escape SQL identifiers and literals in metadata/DDL paths (#1914)#2205HandSonic wants to merge 4 commits into
HandSonic wants to merge 4 commits into
Conversation
…ierProcessor per maintainer review (OtterMind#1914) - new OceanbaseOracleIdentifierProcessor (SPI ISQLIdentifierProcessor): quoteIdentifier with double-quote doubling, escapeString with single-quote doubling - OceanbaseOracleMetaData overrides getSQLIdentifierProcessor(); DDL builder helpers use OceanbaseOracleIdentifierProcessor.INSTANCE - OceanbaseOracleSqlEscapes removed; tests migrated (5 green)
…always-quote for DDL paths (OtterMind#1914) - quoteIdentifier(String) is conditional again: null/blank passthrough, plain non-reserved identifiers returned unquoted (fixes GenericSqlCompletionEngine raw-vs-quoted mismatches); other inputs are double-quote wrapped with embedded-quote doubling - new quoteIdentifierAlways(String) for DDL-generation call sites that require unconditional quoting; quoteIdentifierIgnoreCase is the always-quote SPI variant and delegates to it - processor now extends OracleIdentifierProcessor to inherit the Oracle reserved-keyword set; versioned overload delegates to quoteIdentifier(String) - tests cover conditional and always behaviors incl. null passthrough (10 green)
… empty quoted identifier) (OtterMind#1914)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the SQL-injection hardening tracked in #1914. Prior art: #2052 (Oracle), #2053 (SQL Server), and the wave-1 batch (#2172-#2177).
These are second-order injection paths: values such as table/schema/view/index names originate from the connected database's own metadata, so exploitation requires a maliciously named object in a target database.
What changed (6 sites)
Six literal-interpolation sites in OceanbaseOracleMetaData (tableDDL/comments/index DDL) escaped via new OceanbaseOracleSqlEscapes.
Verification
mvn -B -pl chat2db-community-plugins/chat2db-community-oceanbase-oracle -f chat2db-community-server/pom.xml -Dmaven.test.skip=false -DskipTests=false -Dsurefire.includes=**/*Test.java -Dsurefire.failIfNoSpecifiedTests=false -Dmaven.test.failure.ignore=false testResult: Tests run: 5, Failures: 0, Errors: 0, Skipped: 0.
This branch also passed a two-lens adversarial review (escape-correctness/coverage + regression/test-efficacy); all blocking findings were fixed and re-tested before submission.