Weather Witness

First Flight #40
Beginner FriendlyFoundrySolidityNFT
100 EXP
View results
Submission Details
Severity: low
Valid

Insecure usage of HTTP instead of HTTPS

Root + Impact

Description

  • HTTP requests should be made over secure protocols to prevent MITM (Man-In-The-Middle) attacks and ensure data integrity.

  • In this case, the OpenWeatherMap geocoding API is called via HTTP instead of HTTPS, exposing sensitive data like API keys and parameters to potential interception.

const geoCodingRequest = Functions.makeHttpRequest({
url: "http://api.openweathermap.org/geo/1.0/zip",
...
@> url: "http://api.openweathermap.org/geo/1.0/zip"

Risk

Likelihood:

  • This will occur every time a geocoding request is made, as the URL is hardcoded.

  • All deployments are affected regardless of environment (testnet or mainnet), unless manually fixed.

Impact:

  • API keys and location data can be intercepted in transit.

  • Attackers may alter responses, injecting false latitude/longitude values and causing incorrect weather data to be fetched.

Proof of Concept

None

Recommended Mitigation

- url: "http://api.openweathermap.org/geo/1.0/zip",
+ url: "https://api.openweathermap.org/geo/1.0/zip",
Updates

Appeal created

bube Lead Judge 6 days ago
Submission Judgement Published
Validated
Assigned finding tags:

Use of `http` instead of `https` for getting geo location

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.