# CVE-2024-37163: SkyScrape Secure API Requests


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Jun 2024
- **Updated:** 2 Aug 2024

## What is CVE-2024-37163?

CVE-2024-37163 is a medium-severity vulnerability in oslabs-beta SkyScraper, published on 7 Jun 2024. 

### Official description

SkyScrape is a GUI Dashboard for AWS Infrastructure and Managing Resources and Usage Costs.  SkyScrape's API requests are currently unsecured HTTP requests, leading to potential vulnerabilities for the user's temporary credentials and data.  This affects version 1.0.0.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2024-37163?

It affects 1 product.


Products: Opensourcelabs Skyscraper.

## How do I fix CVE-2024-37163?

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

## Is CVE-2024-37163 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37163 and fix it if it is affected.

What it is: CVE-2024-37163 is a medium-severity vulnerability in oslabs-beta SkyScraper, published on 7 Jun 2024. 
Exploitation: There is no known exploitation of CVE-2024-37163 in the wild and no public exploit code.

Affected product: oslabs-beta SkyScraper. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-37163/ (Markdown: https://insights.sbomify.com/CVE-2024-37163/index.md)
```

## Sources

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

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