CVE-2015-5957
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 · uneditedBuffer overflow in the DumpSysVar function in var.c in Remind before 3.1.15 allows attackers to have unspecified impact via a long name.
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 confidenceBuffer overflow vulnerability in the DumpSysVar function in var.c of the Remind calendar software versions prior to 3.1.15. The function fails to properly validate the length of input (a long name) before copying it into a fixed-size buffer, allowing potential arbitrary code execution or denial of service.
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= 13.1= 13.2<= 3.1.14CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if Remind calendar software is installedRun 'which remind' or 'rpm -qa | grep -i remind' (on RPM-based systems) to locate the remind binary or packageAffected if Remind is not found on the system, then not affected
-
Determine the installed Remind versionRun 'remind -v' or 'remind --version' to display the version numberAffected if The version displayed is 3.1.14 or earlier, or any version prior to 3.1.15
-
Identify the package version on openSUSE systemsRun 'rpm -q remind' to query the installed RPM package version directlyAffected if The package version is 3.1.14-0 or earlier, or shows a version less than 3.1.15
-
Verify the vulnerable var.c component existsCheck if the Remind binary includes the DumpSysVar function by running 'strings $(which remind) | grep -i varsys' or examining the binary's linked librariesAffected if The DumpSysVar functionality is present in the installed binary and the version is below 3.1.15
A user is affected if Remind version 3.1.14 or earlier (or any version prior to 3.1.15) is installed, as the vulnerable DumpSysVar function in var.c contains the buffer overflow flaw.
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.
dbcve · scopedUpgrade to Remind version 3.1.15 or later which contains the fix for this vulnerability.
Remind 3.1.15
- Upgrade Remind to version 3.1.15 or later
- For OpenSUSE systems, run: zypper update remind or zypper in remind to get the patched version
- Verify the installed version by running: remind -v
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5957 — 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-2015-5957 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