dbcve.org
HublinApplication · Linagora

CVE-2019-1010205

HIGH · 7.5 CVSS v3.0 Published 2019-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
LINAGORA hublin latest (commit 72ead897082403126bf8df9264e70f0a9de247ff) is affected by: Directory Traversal. The impact is: The vulnerability allows an attacker to access any file (with a fixed extension) on the server. The component is: A web-view renderer; details here: https://lgtm.com/projects/g/linagora/hublin/snapshot/af9f1ce253b4ee923ff8da8f9d908d02a8e95b7f/files/backend/webserver/views.js?sort=name&dir=ASC&mode=heatmap&showExcluded=false#xb24eb0101d2aec21:1. The attack vector is: Attacker sends a specially crafted HTTP request.

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

A directory traversal vulnerability exists in the hublin web-view renderer (backend/webserver/views.js). The vulnerability allows attackers to craft HTTP requests using '..' path sequences to access arbitrary files on the server that have a fixed extension, bypassing intended directory restrictions.

MitigationImplement strict input validation and path sanitization in the file rendering logic to reject requests containing traversal sequences ('..'), and enforce directory bounds checking to ensure files are accessed only from allowed paths.

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
HublinApplication
Affected:all versions

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hublin installation and version
    Locate the Hublin installation directory and check package.json or version file to confirm the installed version
    Affected if Any version of Linagora Hublin is installed (all versions are affected)
  2. Verify web-view renderer module is present
    Check for the existence of backend/webserver/views.js file in the Hublin installation directory
    Affected if The views.js file exists in the expected path (this file contains the vulnerable code)
  3. Confirm web server is network accessible
    Determine if the Hublin web server is exposed on a network interface (listening on non-loopback address) rather than localhost only
    Affected if The web server is accessible from network addresses, allowing external attackers to send malicious requests
  4. Inspect request handling in views.js
    Open backend/webserver/views.js and examine the code that handles file path parameters for the presence of path traversal validation (look for '..' sequence handling)
    Affected if The code processes file path parameters without rejecting '..' traversal sequences or enforcing directory bounds checks
  5. Test for vulnerable endpoint exposure
    Identify HTTP endpoints in the application that use the views.js renderer to serve files, and determine if they accept path parameters without sanitization
    Affected if File-serving endpoints accept user-controlled path parameters that reach the vulnerable views.js code without validation

A user is affected if Hublin is installed with the web-view renderer accessible over network and the views.js file processes path parameters without rejecting '..' traversal sequences.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and path sanitization in the file rendering logic to reject requests containing traversal sequences ('..'), and enforce directory bounds checking to ensure files are accessed only from allowed paths.

Fix this in Hublin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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