dbcve.org
ChickenApplication · Call Cc

CVE-2013-2075

HIGH · 8.8 CVSS v3.1 Published 2019-10-31
Fix available
A fix is available. Upgrade to after 4.8.0.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Multiple buffer overflows in the (1) R5RS char-ready, (2) tcp-accept-ready, and (3) file-select procedures in Chicken through 4.8.0.3 allows attackers to cause a denial of service (crash) by opening a file descriptor with a large integer value. NOTE: this issue exists because of an incomplete fix for CVE-2012-6122.

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 · high confidence

Multiple buffer overflows exist in Chicken Scheme's runtime (versions through 4.8.0.3) within the R5RS char-ready, tcp-accept-ready, and file-select procedures. These overflows are triggered when processing file descriptors with large integer values, due to incomplete patching from CVE-2012-6122. The vulnerability allows attackers to cause denial of service via crash.

MitigationUpgrade Chicken Scheme to version 4.8.0.4 or later which contains the complete fix. If upgrade is not immediately feasible, implement application-layer controls to validate and cap file descriptor values before passing them to these procedures.

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
ChickenApplication
Affected:<= 4.8.0.3

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Check Chicken Scheme version
    Run `chicken-version` in the Chicken interpreter (csi) or use `csi -version` at command line. Alternatively, check the installed package version via your system's package manager.
    Affected if Version is 4.8.0.3 or earlier (any version through 4.8.0.3)
  2. Identify use of vulnerable R5RS procedures
    Search your application source code for calls to char-ready, tcp-accept-ready, and file-select procedures. These are part of the R5RS runtime and may appear in Scheme code using these procedures.
    Affected if Your application code or dependencies call char-ready, tcp-accept-ready, or file-select with user-controlled file descriptor arguments
  3. Check for large file descriptor handling
    Examine how your application creates or receives file descriptor values. Look for code paths where file descriptors from external sources (network sockets, opened files, pipes) could be passed to the vulnerable procedures.
    Affected if File descriptor values from external sources (network, files, pipes) can reach values larger than typical small integers without validation
  4. Audit TCP server and socket code
    Review any TCP server implementations using tcp-accept-ready, as this procedure is specifically listed as vulnerable. Check how accepted sockets are handled.
    Affected if TCP accept operations are performed using Chicken's tcp-accept-ready procedure
  5. Verify fd-set or select usage
    If using file-select directly or through higher-level abstractions, verify that file descriptor values are validated before being passed. file-select internally uses select() which accepts file descriptor integers.
    Affected if file-select is called with file descriptors that could have large integer values

You are affected if you run Chicken Scheme version 4.8.0.3 or earlier AND your application uses char-ready, tcp-accept-ready, or file-select with file descriptors that could have large integer values.

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.

From vendor data
Upgrade available Upgrade to a release after 4.8.0.3
Interim mitigation

Upgrade Chicken Scheme to version 4.8.0.4 or later which contains the complete fix. If upgrade is not immediately feasible, implement application-layer controls to validate and cap file descriptor values before passing them to these procedures.

Fix this in Chicken Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2075 — 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-2013-2075 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