# Usage of insecure HTTP connection

## Overview

* **Rule ID**: `javascript_lang_http_insecure`
* **Applicable Languages**: Javascriptscript
* **Weakness ID**: CWE-319

## Description

Your application is vulnerable when connecting to APIs via insecure HTTP connections. HTTP does not encrypt data, leaving it exposed to interception and tampering. Ensure your application uses HTTPS for all connections, as it encrypts data in transit and enhances security.

## Remediation Guidelines

* **Avoid** using HTTP for outgoing connections or API calls. This practice exposes your data to risks such as eavesdropping and tampering.

  ```java
  const response = axios.get('http://insecure-api.com') // unsafe

  ```
* **Ensure** that all external connections, particularly API calls, utilize HTTPS to secure data in transit.

  ```java
  const response = axios.get('https://secure-api.com')
  ```

## References

* [**OWASP insecure transport**](https://owasp.org/www-community/vulnerabilities/Insecure_Transport)
* [**CWE-319: Cleartext Transmission of Sensitive Information**](https://cwe.mitre.org/data/definitions/319.html)
* [**OWASP Top 10: A02:2021 - Cryptographic Failures**](https://owasp.org/Top10/A02_2021-Cryptographic_Failures/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)