FedoraOperating system · Fedoraproject
CVE-2019-15237
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 · uneditedRoundcube Webmail through 1.3.9 mishandles Punycode xn-- domain names, leading to homograph attacks.
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 confidenceRoundcube Webmail through version 1.3.9 does not properly validate or handle Punycode-encoded domain names (those prefixed with xn--). This allows attackers to register domain names using visually similar (homoglyph) characters from different scripts that appear identical to legitimate domains, enabling phishing attacks and credential theft.
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
FedoraOperating system
= 29<= 1.3.9CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
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 Roundcube package version on FedoraRun 'rpm -qa | grep roundcube' or 'rpm -q roundcube' to retrieve the installed package versionAffected if The displayed version is 1.3.9 or lower, or the package name indicates roundcube version <= 1.3.9
-
Check Roundcube version via web interfaceAccess the Roundcube login page and look for a version identifier in the footer, or access /?mailcwd (if enabled) to view version informationAffected if The displayed version number is 1.3.9 or any version up to and including 1.3.9
-
Check Roundcube version via configuration fileLocate the Roundcube installation directory and examine the 'program/include/iniset.php' or 'program/lib/Roundcube/bootstrap.php' file, which typically contain a version constantAffected if The version constant defined in the file reads 1.3.9 or lower
-
Determine if Punycode/IDN handling is in useReview the Roundcube configuration file 'config/main.inc.php' for 'login_autocomplete' or 'email_domain' settings, and check if the server processes internationalized domain namesAffected if Internationalized domain name (IDN) support is enabled and the Roundcube version is 1.3.9 or lower, as the vulnerability exists in how Punycode domains are validated
A system is affected if Roundcube Webmail version 1.3.9 or earlier is installed and IDN/Punycode handling is active, enabling homograph phishing attacks.
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 Roundcube Webmail to version 1.4 or later where the Punycode/homograph handling vulnerability is resolved.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15237 — 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-15237 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