An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.

Improper pathname handling in ruby-rack-cors, a middleware that makes Rack-based apps CORS compatible, may result in access to private resources.

The remote Ubuntu 16.04 LTS host has a package installed that is affected by a vulnerability as referenced in the USN-4571-1 advisory.

    It was discovered that rack-cors did not properly handle relative file paths. An attacker could use this     vulnerability to access arbitrary files.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

This package allowed ../ directory traversal to access private resources because resource matching did not ensure that pathnames were in a canonical format.

For Debian 9 stretch, this problem has been fixed in version 0.4.0-1+deb9u2.

We recommend that you upgrade your ruby-rack-cors packages.

For the detailed security status of ruby-rack-cors please refer to its security tracker page at:
https://security-tracker.debian.org/tracker/ruby-rack-cors

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This package allowed ../ directory traversal to access private resources because resource matching did not ensure that pathnames were in a canonical format.

For Debian 8 'Jessie', this problem has been fixed in version 0.2.9-1+deb8u1.

We recommend that you upgrade your ruby-rack-cors packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Gitlab reports :

Path Traversal to Arbitrary File Read

User Permissions Not Validated in ProjectExportWorker

XSS Vulnerability in File API

Package and File Disclosure through GitLab Workhorse

XSS Vulnerability in Create Groups

Issue and Merge Request Activity Counts Exposed

Email Confirmation Bypass Using AP

Disclosure of Forked Private Project Source Code

Private Project Names Exposed in GraphQL queries

Disclosure of Issues and Merge Requests via Todos

Denial of Service via AsciiDoc

Last Pipeline Status Exposed

Arbitrary Change of Pipeline Status

Grafana Token Displayed in Plaintext

Update excon gem

Update rdoc gem

Update rack-cors gem

Update rubyzip gem

ID	Name	Product	Family	Severity
149715	Debian DSA-4918-1 : ruby-rack-cors - security update	Nessus	Debian Local Security Checks	medium
141176	Ubuntu 16.04 LTS : rack-cors vulnerability (USN-4571-1)	Nessus	Ubuntu Local Security Checks	medium
141131	Debian DLA-2389-1 : ruby-rack-cors security update	Nessus	Debian Local Security Checks	medium
133532	Debian DLA-2096-1 : ruby-rack-cors security update	Nessus	Debian Local Security Checks	medium
133434	FreeBSD : Gitlab -- Multiple Vulnerabilities (c5bd9068-440f-11ea-9cdb-001b217b3468)	Nessus	FreeBSD Local Security Checks	critical

Detections

Analytics

CVE-2019-18978

medium

Tenable Plugins

medium

medium

medium

medium

critical