CVE-2024-37163
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 · uneditedSkyScrape 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.
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 confidenceSkyScrape version 1.0.0 transmits API requests over unsecured HTTP instead of HTTPS, exposing AWS temporary credentials and user data to potential interception via man-in-the-middle attacks. This transport-layer vulnerability allows attackers on the same network to sniff sensitive authentication tokens and infrastructure data.
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= 1.0.0CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SkyScrape installation and versionRun 'pip show skyscaper' or check package.json/package-lock.json if Node-based, or check the installed package metadata to confirm version is exactly 1.0.0Affected if Version is 1.0.0
-
Locate SkyScrape configuration fileFind the main configuration file (typically config.yaml, config.json, or .env in the project root or ~/.skyscraper/) that contains API endpoint settingsAffected if Configuration file exists and contains endpoint definitions
-
Check API endpoint protocol settingsInspect the configuration for API_URL, ENDPOINT, or similar fields; verify whether URLs start with 'http://' (insecure) or 'https://' (secure)Affected if Any API endpoint URLs use http:// instead of https://
-
Inspect runtime API request trafficUse network monitoring tools (tcpdump, Wireshark, or proxy) to observe outgoing connections from the SkyScrape client; check if requests go to port 80 (HTTP) or port 443 (HTTPS)Affected if API requests are sent to HTTP (port 80) endpoints
-
Verify credential transmission methodExamine logs or network capture to confirm whether AWS credentials, tokens, or authentication headers are being sent over cleartext HTTP connectionsAffected if Authentication data is transmitted over unencrypted HTTP
Environment is affected if SkyScrape version 1.0.0 is installed AND API communications are configured to use unsecured HTTP instead of HTTPS.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement TLS/HTTPS for all API communications, ensuring certificates are properly configured and the client is updated to validate server certificates.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37163 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37163 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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