# CVE-2013-7111: Exposure of Sensitive Information in bio-basespace-sdk

> Attackers can obtain sensitive API keys by listing processes, exposing credentials in the BaseSpace Ruby SDK.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xwr3-fmgj-mmfr

## What is CVE-2013-7111?

CVE-2013-7111 is a medium-severity vulnerability in n/a, published on 29 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The put_call function in the API client (api/api_client.rb) in the BaseSpace Ruby SDK (aka bio-basespace-sdk) gem 0.1.7 for Ruby uses the API_KEY on the command line, which allows remote attackers to obtain sensitive information by listing the processes.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-7111?

2 open source packages ship an affected version, including bio-basespace-sdk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bio-basespace-sdk` | RubyGems | All versions to 0.1.7 | None |
| `bio-basespace-sdk` | RubyGems | All versions to 0.1.7 | None |

Products: Basespace Ruby Sdk Project Basespace Ruby Sdk.

## How do I fix CVE-2013-7111?

No fix has been published for CVE-2013-7111 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-7111 being exploited?

There is no known exploitation of CVE-2013-7111 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7111 and fix it if it is affected.

What it is: CVE-2013-7111 is a medium-severity vulnerability in n/a, published on 29 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7111 in the wild and no public exploit code.

Affected packages and fixed versions:
- bio-basespace-sdk (RubyGems): affected all versions up to 0.1.7; no fix listed
- bio-basespace-sdk (RubyGems): affected all versions up to 0.1.7; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-7111/ (Markdown: https://insights.sbomify.com/CVE-2013-7111/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-7111
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-7111
- OSV: https://osv.dev/vulnerability/CVE-2013-7111

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-7111/
Summaries are generated and may contain mistakes; the official description above is the record.