Skip to main content
Participant
September 10, 2026
Question

Has anyone else experienced problems implementing CF23 update 24

  • September 10, 2026
  • 9 replies
  • 59 views

Has anyone else experienced problems implementing CF23 update 24 where it seems to be complaining about the colon in the dbvarname. The procedure name is just PACKAGE.PROCEDURE_NAME I don't see the cause of the problem. Actual error: The value ":v_session_id" contains invalid characters. cfprocparam dbvarname=":v_session_id" value="#functionHere()#" type="IN" cfsqltype="cf_sql_varchar"

    9 replies

    Participant
    September 10, 2026

    Yes, we experienced the same issue.  We get this error with the colon in place:

    "Error","ajp-nio-127.0.0.1-8122-exec-7","09/10/26","13:46:10","Background Processes","The value ":p_phone_num" contains invalid characters.Only letters, digits, and the characters _ $ # @ are allowed in a SQL identifier such as a stored procedure name or bind variable name (a dotted procedure name may also contain "."). The value was rejected to prevent SQL injection through the identifier.

     

    and this error when the colon is removed:

    "Error","ajp-nio-127.0.0.1-8122-exec-1","09/10/26","13:46:41","Background Processes","Error Executing Database Query.[Macromedia][Oracle JDBC Driver][Oracle]ORA-06502: PL/SQL: numeric or value error: character to number conversion error
    ORA-06512: at line 1

     

    So, seems like the colon is both required and not allowed.  We had to uninstall Update 24.

    Participant
    September 11, 2026

    You can use JVM arguments to get around it.

    -Dcoldfusion.sql.allowUnsafeStoredProcIdentifiers=true

    Charlie Arehart
    Community Expert
    Community Expert
    September 11, 2026

    To be clear, that's what I was referring to in my replies yesterday and today. 

    /Charlie (troubleshooter, carehart. org)
    Charlie Arehart
    Community Expert
    Community Expert
    September 10, 2026

    @SammyBridger, it's unclear: have you read the technote for the update, about the changes related to cfstoredproc, and more? If so, please clarify if the available jvm arg mitigation resolves things, and then if so are you asking WHY your code now fails that new security protection? ( Please don't skip to asking that last question here. The first two are important for us to know, for context.) 

    /Charlie (troubleshooter, carehart. org)
    Participant
    September 11, 2026

    Hi Charlie, yes tech note read. The example they provide of good and bad calls does not contain any procparams. All our procedure names are plain text, either procedure_name or PACKAGE.procedure_name etc. The dbvarnames (with the exception of the colon that Adobe introduced) all are plain text too. We basically would have to remove all dbvarnames from the code base in order to avoid using the JVM arguments to keep the site functional. Doesn’t seem right personally. Did they test this update with Oracle database stored procs?

    Charlie Arehart
    Community Expert
    Community Expert
    September 11, 2026

    All that said, did you try the jvm flag? If it helps, then you can ask them why the change affected you in a way not communicated.

     

    As for your final question, I can't answer. I don't work for them, nor even WITH them in any way on updates. 

    /Charlie (troubleshooter, carehart. org)