Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-5mmw-p5qv-w3x5

MEDIUM

GHSA-5mmw-p5qv-w3x5 is a medium-severity (CVSS 5.3) CWE-345 vulnerability in github.com/mojocn/base64Captcha. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-5mmw-p5qv-w3x5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Always incorrect control flow in github.com/mojocn/base64Captcha

Also known asCVE-2023-45292GO-2023-2386
Published
Dec 12, 2023
Updated
Dec 14, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected
🐹github.com/mojocn/base64Captcha

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

When using the default implementation of Verify to check a Captcha, verification can be bypassed. For example, if the first parameter is a non-existent id, the second parameter is an empty string, and the third parameter is true, the function will always consider the Captcha to be correct.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/mojocn/base64Captchaall versions1.3.6
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mojocn/base64Captcha. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/mojocn/base64Captcha to 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5mmw-p5qv-w3x5 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5mmw-p5qv-w3x5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5mmw-p5qv-w3x5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When using the default implementation of Verify to check a Captcha, verification can be bypassed. For example, if the first parameter is a non-existent id, the second parameter is an empty string, and the third parameter is true, the function will always consider the Captcha to be correct.
O3 Security · Impact-Aware SCA

Is GHSA-5mmw-p5qv-w3x5 in your dependencies?

O3 detects GHSA-5mmw-p5qv-w3x5 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.