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

cve.new
GHSA-pfrr-xvrf-pxjxhigh8.7

Laravel Reverb Missing API Signature Verification

Check your stack

The advisory, in context

Impact

A community member disclosed an issue where verification signatures for requests sent to Reverb's Pusher-compatible API were not being verified. This API is used in scenarios such as broadcasting a message from a backend service or for obtaining statistical information (such as number of connections) about a given channel.

The verification signature is a hash comprised of different parts of the request signed by the app's secret key. The signature is sent as part of the request and should be regenerated by Reverb. Only when both the signature in the request and the one generated by Reverb match should the request be allowed. This helps to verify the request came from a known source.

[!NOTE]
This issue only affects the Pusher-compatible API endpoints and not the WebSocket connections themselves. In order to exploit this vulnerability, the application ID which, should never be exposed, would need to be known by an attacker.

The following endpoints were affected:

POST /events
POST /events_batch
GET /connections
GET /channels
GET /channel
GET /channel_users
POST /users_terminate

Patches

The issue was resolved by #252 and the patch released in v1.4.0.

References

Generating Pusher authentication signatures

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.

Ecosystem versions

Earlier releases before 1.4.0

Fixed in 1.4.0

19 explicitly affected versions

v1.0.0, v1.0.0-beta1, v1.0.0-beta10, v1.0.0-beta11, v1.0.0-beta12, v1.0.0-beta13, v1.0.0-beta14, v1.0.0-beta2, v1.0.0-beta3, v1.0.0-beta4, v1.0.0-beta5, v1.0.0-beta6, v1.0.0-beta7, v1.0.0-beta8, v1.0.0-beta9, v1.1.0, v1.2.0, v1.3.0, v1.3.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.4.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v1.0.0",
    "v1.0.0-beta1",
    "v1.0.0-beta10",
    "v1.0.0-beta11",
    "v1.0.0-beta12",
    "v1.0.0-beta13",
    "v1.0.0-beta14",
    "v1.0.0-beta2",
    "v1.0.0-beta3",
    "v1.0.0-beta4",
    "v1.0.0-beta5",
    "v1.0.0-beta6",
    "v1.0.0-beta7",
    "v1.0.0-beta8",
    "v1.0.0-beta9",
    "v1.1.0",
    "v1.2.0",
    "v1.3.0",
    "v1.3.1"
  ]
}

References