CVE-2017-7414
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 · uneditedIn Horde_Crypt before 2.7.6, as used in Horde Groupware Webmail Edition 5.x through 5.2.17, OS Command Injection can occur if the user has PGP features enabled in the user's preferences, and has enabled the "Should PGP signed messages be automatically verified when viewed?" preference. To exploit this vulnerability, an attacker can send a PGP signed email (that is maliciously crafted) to the Horde user, who then must either view or preview it.
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 confidenceOS command injection vulnerability in Horde_Crypt's PGP message handling. When users have PGP enabled with automatic verification of signed messages, viewing or previewing a maliciously crafted PGP signed email triggers OS command execution. Affected versions include Horde Groupware Webmail Edition 5.x through 5.2.17 and Horde_Crypt before 2.7.6.
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= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.1.0= 5.1.1= 5.1.2= 5.1.3= 5.1.4= 5.1.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Horde Groupware versionLocate the version file or admin interface that displays the Horde Groupware version number (typically found in version.php, lib/Version.php, or the administration panel under system information)Affected if The installed version is 5.x through 5.2.17 (versions 5.0.0 through 5.2.17 are affected)
-
Identify installed Horde_Crypt versionLocate the Horde_Crypt library version file (typically in the pear/Horde_Crypt directory or lib/Horde/Crypt/version.php)Affected if The Horde_Crypt version is before 2.7.6 (versions 2.7.5 and earlier are affected)
-
Verify PGP support is enabledCheck the Horde configuration for PGP/Crypt settings - look for enable_pgp or similar configuration flags in the global configuration files (horde/config/conf.xml or horde/config/prefs.php)Affected if PGP support is turned ON in the Horde configuration (the vulnerability only applies when PGP is enabled)
-
Check if automatic signed message verification is enabledExamine the user preference or global setting for automatic verification of PGP-signed messages (typically found in the Crypt preferences panel under Mail settings, or in the horde/config/prefs.php file under crypt preferences)Affected if Automatic verification of signed messages is enabled - this is the specific trigger condition for the flaw
A user is affected if they are running Horde Groupware 5.x through 5.2.17 or Horde_Crypt before 2.7.6, AND have PGP enabled with automatic verification turned on for signed messages.
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 dataUpgrade Horde_Crypt to version 2.7.6 or later, or disable the automatic PGP signed message verification preference as an interim workaround.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7414 — 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-2017-7414 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