Debian LinuxOperating system · Debian
CVE-2019-7659
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 · uneditedGenivia gSOAP 2.7.x and 2.8.x before 2.8.75 allows attackers to cause a denial of service (application abort) or possibly have unspecified other impact if a server application is built with the -DWITH_COOKIES flag. This affects the C/C++ libgsoapck/libgsoapck++ and libgsoapssl/libgsoapssl++ libraries, as these are built with that flag.
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 confidenceGenivia gSOAP versions 2.7.x and 2.8.x before 2.8.75 contain a vulnerability in the cookie handling code when built with the -DWITH_COOKIES flag. Attackers can trigger this vulnerability to cause application abort (denial of service) or potentially achieve unspecified other impact by sending specially crafted cookie data to affected server applications using libgsoapck/libgsoapck++ or libgsoapssl/libgsoapssl++ libraries.
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
Debian LinuxOperating system
= 8.0>= 2.7.0, <= 2.7.17>= 2.8.0, < 2.8.75CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify gSOAP versionCheck the installed gSOAP version by reviewing library files, headers, or the application's dependency information. Look for files like 'gsoap_version.h' or use commands like 'dpkg -l | grep gsoap' on Debian systems, or check the binary/library metadata.Affected if Version is 2.7.0 through 2.7.17, or 2.8.0 through 2.8.74
-
Verify cookie support was compiled inExamine the build configuration or binary to determine if -DWITH_COOKIES was used during compilation. This may be found in build logs, compile flags, or by inspecting the binary with tools like 'strings' or 'objdump' for cookie-related symbols.Affected if The library was built with the -DWITH_COOKIES compile flag enabled
-
Identify application using cookie handlingReview application code or documentation to determine if it uses the cookie handling functionality provided by libgsoapck, libgsoapck++, libgsoapssl, or libgsoapssl++ libraries.Affected if The application links against and uses cookie-enabled gSOAP libraries for HTTP cookie processing
You are affected if your gSOAP version falls within 2.7.0-2.7.17 or 2.8.0-2.8.74, was built with -DWITH_COOKIES, and your application processes HTTP cookies using gSOAP.
Generated from the published advisory. Verify against your own configuration.
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 data2.8.75
Upgrade gSOAP to version 2.8.75 or later. If immediate upgrade is not feasible and cookie functionality is not required, rebuilding without the -DWITH_COOKIES flag will remove the attack surface.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7659 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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