concatenated

Examples: value stored in a table is concatenated into a query without escapement, leaving it vulnerable to injection.

This most likely means that entire programs and libraries can be concatenated and still remain valid.

As an example, on a previous project all of the javascript libraries + the app concatenated together at 3MB.

They could have chosen a different algorithm, or perhaps called the random number generator twice and concatenated the bits.

Apache wants them to be in a separate file, nginx wants them concatenated with the main certificate.

So it doesn't really make sense in context that the salt, pepper, and password were concatenated and passed to bcrypt.

Notice how the the column names (denoted by name) is actually the value of the clustering key concatenated with the actual column name.

I cannot understand why anyone would opt for concatenated SQL over parameterized queries when both were available.

You should work from the premise that there is no safe concatenated string query (regardless of the corner cases where that isn't true).

They then concatenated the temp from tree data for the time when they didn't have temp data with the temp data that they did have.

SQL injection was only beginning to be understood by most developers, many (most?) sites used SQL queries made with unescaped concatenated strings and were vulnerable.

In that stored proc, two of the parameters were concatenated into a select which was then eval-ed, thus leading to a very serious injection possibility.

For example: "what is the outcome of 'is A true' converted to string and concatenated by the outcome of 'is B true'"?

Cappuccino has a completely custom loader and concatenated file format that creates a file system representation, such that when you do something akin to XHR("something/blah") it knows that it already downloaded it and gives it to you without a request, that way whether you ship concatenated code or not the code that fetches it is the same.

Explanation for non-Rails users: the above code causes the five specified Javascript files to be concatenated into "all.js" the first time any page on the Rails site is rendered, and all pages load all.js rather than loading the five Javascript files.

What you need to be doing is replacing your concatenated string queries with precompiled parameterized queries, where the values in your queries are replaced with placeholder strings (like "?" and ":varname"), and the values are passed in a seperate call.