expressjs / expressjs/session

express-session connect.sid trips application gateway's "SQL Hex Encoding Identified" rules

Open
#1,095 0 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
JavaScript
Stars
6.4k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

Hi all,
Our ExpressJS app uses express-session to set a session cookie:

``` .use(
expressSession({
secret: process.env.CLIENT_SECRET,
resave: false,
rolling: true,
saveUninitialized: true,
store: new PGSessionStore(),
cookie: {
secure: process.env.ENV==='production'
httpOnly: false,
maxAge: 1000 * 60 * 10,
},
})
)
```

However, our application gateway blocks some requests to the app because of the generated 'connect.sid'. Specifically, it spits out a "SQL Hex Encoding Identified" message based on its regex rules against SQL injections. Given that the sid is randomly generated, this isn't too surprising - but I can find surprisingly little discussion of this problem online and I'm looking for some guidance on this matter.

What are your thoughts on this issue? Do you have any recommendations on the best `genid` to use in this case without compromising on security?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.