Skip to content

Discuss and implement solution for DBMS specific detection/enumeration limitations #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bdamele opened this issue Jun 26, 2012 · 1 comment
Labels

Comments

@bdamele
Copy link
Member

bdamele commented Jun 26, 2012

Discuss and implement solution for DBMS specific detection/enumeration limitations:

  • Firebird needs a proper string unescaping - but we don't know (in time of testing) the version of the backend firebird, hence we don't know if the unescaping meant for the >=2.1 will work on it.
  • IBM DB2 needs the UNION payload with exact datatypes to detect/exploit UNION query SQLi - NULL does not work, one number for each column neither if the data type is varchar, etc.
@ghost ghost assigned stamparm Jun 26, 2012
@SQLmapTester SQLmapTester mentioned this issue Nov 8, 2012
Closed
@chym chym mentioned this issue Nov 10, 2012
This was referenced Mar 3, 2014
Closed
Closed
@digininja digininja mentioned this issue Aug 12, 2014
@WilliJoin WilliJoin mentioned this issue Aug 29, 2014
This was referenced Nov 17, 2014
@SQLmapTester SQLmapTester mentioned this issue Mar 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants