dbcve.org
CookieApplication · Cookie Project

CVE-2017-18589

HIGH · 7.5 CVSS v3.0 Published 2019-08-26
Fix available
A fix is available. Upgrade to 0.7.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An issue was discovered in the cookie crate before 0.7.6 for Rust. Large integers in the Max-Age of a cookie cause a panic.

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

The Rust cookie crate before version 0.7.6 panics when parsing cookies containing large integer values in the Max-Age attribute, causing denial of service due to unchecked integer overflow.

MitigationUpgrade the cookie crate to version 0.7.6 or later, and validate any cookie Max-Age values before processing to prevent excessively large integers.

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
CookieApplication
Affected:< 0.7.6

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Locate the cookie crate dependency
    Search your project's Cargo.toml file for 'cookie' under the [dependencies] section, or search for 'name = "cookie"' in your Cargo.lock file
    Affected if The cookie crate is listed as a dependency
  2. Identify the installed cookie crate version
    Check the version number specified next to the cookie dependency in Cargo.toml (e.g., cookie = "0.1" or cookie = "0.7.0"), or find the version entry for cookie in Cargo.lock
    Affected if A version number is explicitly specified for the cookie crate
  3. Compare the version to the affected range
    Compare your installed version number to the affected range: versions less than 0.7.6 are vulnerable
    Affected if The version is less than 0.7.6 (for example, 0.7.5, 0.7.0, 0.6.0, etc.)
  4. Check for cookie Max-Age parsing
    Search your codebase for code that parses HTTP cookies and accesses the Max-Age attribute (look for .max_age(), .age(), or similar method calls on parsed Cookie objects)
    Affected if Your application parses cookies and processes the Max-Age attribute

Your environment is affected if the cookie crate version is less than 0.7.6 AND your application parses cookies containing Max-Age attributes with potentially 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 0.7.6 or later
Fixed in 0.7.6
Interim mitigation

Upgrade the cookie crate to version 0.7.6 or later, and validate any cookie Max-Age values before processing to prevent excessively large integers.

Fix this in Cookie Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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