dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-30292

CRITICAL · 10.0 CVSS v3.1 Published 2022-05-04
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap-based buffer overflow in sqbaselib.cpp in SQUIRREL 3.2 due to lack of a certain sq_reservestack call.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Heap-based buffer overflow in sqbaselib.cpp in SQUIRREL 3.2 scripting language library. The vulnerability stems from a missing sq_reservestack call that should reserve stack memory before certain operations, leading to insufficient buffer allocation and subsequent heap overflow when the reserved stack capacity is exceeded.

MitigationApply vendor patch for SQUIRREL 3.2 that adds the missing sq_reservestack call in sqbaselib.cpp, or upgrade to a patched version if available; prioritize given CRITICAL severity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 35= 36
SquirrelApplication
Affected:= 3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Squirrel version
    Run 'squirrel --version' or check the library file version. If using a package manager, run 'rpm -qa | grep squirrel' on Fedora or check installed packages via your package manager. Also check for libsqstdlib or sqbase libraries: 'ldconfig -p | grep squirrel' or inspect the compiled binary/library for version strings.
    Affected if The installed version is exactly 3.2 or falls within the affected range (Squirrel 3.2, Fedora 35 or 36).
  2. Locate the vulnerable library file
    Find the sqbaselib.cpp compiled library: typical paths include /usr/lib/, /usr/local/lib/, or within the application's bundle. Search for 'sqbaselib' files: 'find / -name '*sqbase*' -o -name '*squirrel*' 2>/dev/null'. Check file properties to confirm it belongs to Squirrel 3.2.
    Affected if The sqbaselib library from Squirrel 3.2 is present on the system.
  3. Verify the missing sq_reservestack call in source or binary
    If source code is available, grep for 'sq_reservestack' in sqbaselib.cpp around the vulnerable functions. If only the binary/library is available, check if the binary contains symbols or strings related to stack reservation: 'strings libsqstdlib.so | grep -i reserve' or use disassembler analysis to check if sq_reservestack is invoked before stack-intensive operations.
    Affected if The sq_reservestack call is missing before stack operations that could exceed buffer capacity, indicating the unpatched version.
  4. Check application configuration for vulnerable stack usage
    Review application logs, configurations, or code that invokes Squirrel interpreter functions that trigger the affected sqbaselib.cpp functions (typically those involving string manipulation or array operations that push many items onto the stack). Look for scripts that pass large input or create large arrays.
    Affected if The application uses Squirrel scripts or configurations that could trigger stack operations exceeding the unreserved capacity, leading to heap overflow.

A system is affected if it runs Squirrel version 3.2 or ships the unpatched sqbaselib library from that version, particularly on Fedora 35 or 36, and executes scripts or operations that push data onto the Squirrel stack beyond allocated buffer capacity.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Apply vendor patch for SQUIRREL 3.2 that adds the missing sq_reservestack call in sqbaselib.cpp, or upgrade to a patched version if available; prioritize given CRITICAL severity.

Recommended fix High confidence

Squirrel 3.2.1 or later version containing the fix (check GitHub releases for availability)

  1. 1. Navigate to the Squirrel source code directory containing sqbaselib.cpp
  2. 2. Locate the function that handles stack operations where sq_reservestack is missing
  3. 3. Apply the fix from commit a6413aa690e0bdfef648c68693349a7b878fe60d which adds the sq_reservestack call to prevent heap-based buffer overflow
  4. 4. Recompile the Squirrel interpreter/library with the patched source code
  5. 5. Replace the existing squirrel interpreter/library binaries with the newly compiled fixed versions
  6. 6. Verify the fix by testing the interpreter with the previously vulnerable code paths

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30292 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data