Status/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)
Created: 03/09/2016
Components: Security Analyzer
Versions: 2016
Failure Type: Unspecified
Found In Build/Fixed In Build: Alpha_v31 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Win All
Vote Count: 0
<cfquery>
INSERT INTO someTable (
uuid
)VALUES(
’#createUuid()#’
)
</cfquery>
<cfquery name="uuids">
SELECT ’#createUuid()#’ AS uuid
FROM someTable
</cfquery>
<cfset queryExecute("
INSERT INTO someTable (
uuid
)VALUES(
’#createUuid()#’
)
")>
<cfset uuids = queryExecute("
SELECT ’#createUuid()#’ AS uuid
FROM someTable
")>
The first INSERT just gets a warning; the first SELECT gets an error (if anything... should it not be the other way around? And obviously neither is actually a problem.
And apparently queryExecute() is not vulnerable in these ways, as I get no notifications on those statements.
I have to ask... is this feature ready for testing yet? Should I just leave it be?
Note: I am not specifically trying to defeat it, these examples I’m posting are reduced-complexity repro cases of actual "issues" being reported when I test proper code.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 4126680
External Customer Info:
External Company: Straker Interactive
External Customer Name: Adam Cameron
External Customer Email: CAMERON.ADAM@GMAIL.COM
External Test Config:Attachments:
Comments: