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
All vulnerabilities
GHSA-6gvq-jcmp-8959medium6.5

ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay

Check your stack

The advisory, in context

Impact

A cryptographic semantic binding flaw in ALTCHA libraries allows challenge payload splicing, which may enable replay attacks. The HMAC signature does not unambiguously bind challenge parameters to the nonce, allowing an attacker to reinterpret a valid proof-of-work submission with a modified expiration value. This may allow previously solved challenges to be reused beyond their intended lifetime, depending on server-side replay handling and deployment assumptions.

The vulnerability primarily impacts abuse-prevention mechanisms such as rate limiting and bot mitigation. It does not directly affect data confidentiality or integrity.

Patches

This issue has been addressed by enforcing explicit semantic separation between challenge parameters and the nonce during HMAC computation.

Users are advised to upgrade to patched versions.

Workarounds

As a mitigation, implementations may append a delimiter to the end of the salt value prior to HMAC computation (for example, <salt>?expires=<time>&). This prevents ambiguity between parameters and the nonce and is backward-compatible with existing implementations, as the delimiter is treated as a standard URL parameter separator.

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.

Semantic versions

Earlier releases before 1.4.1

Fixed in 1.4.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.4.1"
        }
      ],
      "type": "SEMVER"
    }
  ],
  "versions": []
}
Ecosystem versions

Earlier releases before 1.3.1

Fixed in 1.3.1

11 explicitly affected versions

v0.1.0, v0.1.1, v0.1.2, v0.1.3, v0.1.4, v1.0.0, v1.1.0, v1.1.1, v1.1.2, v1.2.0, v1.3.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.3.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v0.1.0",
    "v0.1.1",
    "v0.1.2",
    "v0.1.3",
    "v0.1.4",
    "v1.0.0",
    "v1.1.0",
    "v1.1.1",
    "v1.1.2",
    "v1.2.0",
    "v1.3.0"
  ]
}
Semantic versions

Earlier releases before 1.0.0

Fixed in 1.0.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.0.0"
        }
      ],
      "type": "SEMVER"
    }
  ],
  "versions": []
}
Ecosystem versions

Earlier releases before 1.3.0

Fixed in 1.3.0

4 explicitly affected versions

1.1.0, 1.1.1, 1.1.2, 1.2.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.3.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.1.0",
    "1.1.1",
    "1.1.2",
    "1.2.0"
  ]
}
altcha RubyGems
Ecosystem versions

Earlier releases before 1.0.0

Fixed in 1.0.0

3 explicitly affected versions

0.1.0, 0.2.0, 0.2.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.0.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "0.1.0",
    "0.2.0",
    "0.2.1"
  ]
}
Ecosystem versions

Earlier releases before 1.0.0

Fixed in 1.0.0

10 explicitly affected versions

0.1.0, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.2.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.0.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "0.1.0",
    "0.1.2",
    "0.1.3",
    "0.1.4",
    "0.1.5",
    "0.1.6",
    "0.1.7",
    "0.1.8",
    "0.1.9",
    "0.2.0"
  ]
}
Semantic versions

Earlier releases before 1.0.0

Fixed in 1.0.0

2 explicitly affected versions

0.1.0, 0.2.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "1.0.0"
        }
      ],
      "type": "SEMVER"
    }
  ],
  "versions": [
    "0.1.0",
    "0.2.0"
  ]
}

References