GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Check your stack
GHSA-5pv8-ppvj-4h68medium5.3

Prevent user enumeration using Guard or the new Authenticator-based Security

Impact

The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.

Source excerpt · OSV

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Affected rangeRecorded fix
From 5.0.0 before 5.2.8Ecosystem versions5.2.8
From 2.8.0 before 3.4.49Ecosystem versions3.4.49
From 4.0.0 before 4.4.24Ecosystem versions4.4.24

Version evidence: OSV · GHSA-5pv8-ppvj-4h68

View original version evidence (260 explicit versions)
Affected rangeRecorded fix
From 2.8.0 before 3.4.48Ecosystem versions3.4.48
From 4.0.0 before 4.4.23Ecosystem versions4.4.23
From 5.0.0 before 5.2.8Ecosystem versions5.2.8

Version evidence: OSV · GHSA-5pv8-ppvj-4h68

View original version evidence (293 explicit versions)
Affected rangeRecorded fix
From 2.8.0 before 3.4.48Ecosystem versions3.4.48
From 4.0.0 before 4.4.23Ecosystem versions4.4.23
From 5.0.0 before 5.2.8Ecosystem versions5.2.8

Version evidence: OSV · GHSA-5pv8-ppvj-4h68

View original version evidence (298 explicit versions)
Affected rangeRecorded fix
From 2.0.0 before 2.10.7Ecosystem versions2.10.7
From 2.11.0 before 2.11.3Ecosystem versions2.11.3

Version evidence: OSV · GHSA-5pv8-ppvj-4h68

View original version evidence (37 explicit versions)
Affected rangeRecorded fix
From 1.27.0 before 1.29.2Ecosystem versions1.29.2
From 1.30.0 before 1.31.1Ecosystem versions1.31.1

Version evidence: OSV · GHSA-5pv8-ppvj-4h68

View original version evidence (8 explicit versions)
Affected rangeRecorded fix
From 5.1.0 before 5.2.8Ecosystem versions5.2.8

Version evidence: OSV · GHSA-5pv8-ppvj-4h68

View original version evidence (25 explicit versions)
Affected rangeRecorded fix
From 2.8.0 before 3.4.49Ecosystem versions3.4.49
From 4.0.0 before 4.4.24Ecosystem versions4.4.24
From 5.0.0 before 5.2.9Ecosystem versions5.2.9

Version evidence: OSV · GHSA-5pv8-ppvj-4h68

View original version evidence (303 explicit versions)

Original source description

Description

The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.

Resolution

We now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.

The patch for this issue is available here for branch 3.4.

Credits

I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.

References