130n@calvinlai.com
  • About Calvin Lai (fkclai)
  • My Work
  • Cyber Security
    • Cyber Security Centre (CSC)
      • Why we need a CSC
      • CSC Team Structure: Roles, Functions, and Tools
        • Key Function & Role
        • Tools & Platforms
        • People
        • Outsource Strategy
      • HRMC Executive Paper
  • Detection and Response
    • Playbook: Threat Prioritization & Automated Response Strategies
      • Scenario: Detecting and Mitigating a Ransomware Attack
      • Scenario: DC Sync Attack Detected and Mitigated
      • Scenario: Pass-the-Hash (PtH) Attack Detected and Contained
      • Scenario: Phishing Campaign with Malware / Credential Theft Detected and Mitigated
  • Application Architecture
    • Comparison of MVC , N-tier and Microservice Architecture
  • Application Security
    • OAuth, SAML, and OpenID Connect: Key Differences and Use Cases
    • Secure Coding Principles
    • HTTP Header Security Principles
    • Mitigating Broken Object Level Authorization (BOLA)
    • Spring Boot Validation
    • Output Encoding in JavaServer Faces (JSF)
    • Session Management Security Issues
    • Common API Security Problems
      • Broken Authentication
      • Excessive Data Exposure
      • Lack of Resources & Rate Limiting
      • Broken Function Level Authorization
      • Unsafe Consumption of APIs
    • JAVA Exception Handling
    • File Upload Validation
    • OAuth 2.0 Security
      • Insecure Storage of Access Tokens
    • Microservice Security
      • Sample Coding Demo
        • Service Implementation
        • Client Interaction
      • Security Solution for Microservices Architecture
    • Modifying and Protecting Java Class Files
      • Modify a Class File Inside a WAR File
      • Direct Bytecode Editing
        • Steps to Directly Edit a Java Class File
          • Update: Java Bytecode Editing Tools
      • Techniques to Protect Java Class Files
        • Runtime Decryption in WebLogic
    • JAVA Program
      • Secure, Concurrent Web Access Using Java and Tor
      • Creating a Maven Java project in Visual Studio Code
  • Exploit/CVE PoC
    • ZeroLogon Exploit
    • Remote Retrieved Chrome saved Encrypted Password
    • Twitter Control an RCE attack
  • Hacking Report (HTB)
    • Hits & Summary
      • Tools & Cheat Sheet
    • Windows Machine
      • Love 10.10.10.239
      • Blackfield 10.10.10.192
      • Remote 10.10.10.180
      • Sauna 10.10.10.175
      • Forest 10.10.10.161
      • Sniper
      • Json
      • Heist
      • Blue
      • Legacy
      • Resolute
      • Cascade
    • Linux Machine
      • Photobomb 10.10.11.182
      • Pandora 10.10.11.136
      • BountyHunter 10.10.11.100
      • CAP 10.10.10.245
      • Spectra 10.10.10.229
      • Ready 10.10.10.220
      • Doctor 10.10.10.209
      • Bucket 10.10.10.212
      • Blunder 10.10.10.191
      • Registry 10.10.10.159
      • Magic
      • Tabby
  • Penetration Testing
    • Web Application PenTest
    • Network/System PenTest
    • Mobile Penetration Test
      • Certificate Pinning
        • Certificate Pinning Bypass (Android)
          • Root a Android Device
          • Setup Proxy Tool - Burp Suite
      • Checklist
  • Threat Intelligence
    • Advanced Persistent Threat (APT) groups
      • North Korean APT Groups
      • Chinese APT Groups
      • Russian APT Groups
      • Other APT
  • Red Team (Windows)
    • 01 Reconnaissance
    • 02 Privileges Escalation
    • 03 Lateral Movement
    • 04 AD Attacks
      • DCSync
    • 05 Bypass-Evasion
    • 06 Kerberos Attack
    • 99 Basic Command
  • Exploitation Guide
    • 01 Reconnaissance
    • 02 Port Enumeration
    • 03 Web Enumeration
    • 04 Windows Enum & Exploit
      • Windows Credential Dumping
        • Credential Dumping: SAM
        • Credential Dumping: DCSync
      • Kerberos Attack
      • RDP
    • 05 File Enumeration
    • 06 Reverse Shell Cheat Sheet
      • Windows Reverse Shell
      • Linux Reverse Shell
    • 07 SQL Injection
    • 08 BruteForce
    • 09 XSS Bypass Checklist
    • 10 Spring Boot
    • 11 WPA
    • 12 Payload list
  • Vuln Hub (Writeup)
    • MrRobot
    • CYBERRY
    • MATRIX 1
    • Node-1
    • DPwwn-1
    • DC7
    • AiWeb-2
    • AiWeb-1
    • BrainPan
  • CTF (Writeup & Tips)
    • CTF Tools & Tips
    • Hacker One
    • CTF Learn
    • P.W.N. University - CTF 2018
    • HITCON
    • Pwnable
      • 01 Start
  • Useful Command/Tools
    • Kali
    • Windows
    • Linux
  • Offensive Security Lab & Exam
    • Lab
    • Tools for an Offensive Certification
      • Strategy for an Offensive Exam Certification
        • CVEs
        • Privilege Escalation
        • Commands
        • Impacket
  • ISO 27001
    • Disclaimer
    • What is ISO 27001
      • Implementation
    • Documentation
    • Common Mistake
    • Q&A
      • Can internal audit to replace the risk assessment
      • Is it sufficient for only the IT department head to support the ISO 27001 program
      • Does the Business Continuity Plan (BCP) and a Disaster Recovery Plan (DRP) are the same?
    • ISO 27001 Controls and Domains
      • 1. Information Security Policies
      • 2. Organization of Information Security
      • 3. Human Resource Security
      • 4. Asset Management
      • 5. Access Control
      • 6. Cryptographic Controls
      • 7. Physical and Environmental Security
      • 8: Operational Security
      • 9. Communications Security
      • 10. System Acquisition, Development, and Maintenance
      • 11. Supplier Relationships
      • 12: Information Security Incident Management
      • 13. Information Security Aspects of Business Continuity Management
      • 14. Compliance
Powered by GitBook
On this page
  • What is Unsafe Consumption of APIs?
  • Vulnerable Code and Secure Code Example
  • Attack Scenario
  • Insecure Implementation (Prone to Unsafe Consumption of APIs)
  • Attack Payload Example:
  • Secure Implementation (Mitigating Unsafe Consumption of APIs)
  • Key Points for Developers
  • Summary and Key Takeaways
  • Reference Links

Was this helpful?

  1. Application Security
  2. Common API Security Problems

Unsafe Consumption of APIs

What is Unsafe Consumption of APIs?

Unsafe Consumption of APIs occurs when an application consumes external APIs without properly handling potential security risks. This can lead to several security issues, including data breaches, denial of service attacks, and exposure to malicious data.

Maps to OWASP Top 10

Unsafe Consumption of APIs is categorized under A10:2021 - Server-Side Request Forgery (SSRF) in the OWASP Top 10. It emphasizes the importance of securely consuming APIs to prevent exposure to security vulnerabilities.

Vulnerable Code and Secure Code Example

Attack Scenario

Imagine an application that consumes an external API to fetch user data. Without proper validation and error handling, the application might be exposed to malicious data, leading to security vulnerabilities.

Insecure Implementation (Prone to Unsafe Consumption of APIs)

@RestController
@RequestMapping("/api")
public class ExternalApiController {

    @GetMapping("/fetchData")
    public ResponseEntity<?> fetchData(@RequestParam String apiUrl) {
        // Fetch data from external API without validation
        RestTemplate restTemplate = new RestTemplate();
        String response = restTemplate.getForObject(apiUrl, String.class);
        return ResponseEntity.ok(response);
    }
}

Attack Payload Example:

curl http://localhost:8080/api/fetchData?apiUrl=http://malicious.com/data

In this case, the application fetches data from a potentially malicious URL without any validation or error handling.

Secure Implementation (Mitigating Unsafe Consumption of APIs)

@RestController
@RequestMapping("/api")
public class ExternalApiController {

    @GetMapping("/fetchData")
    public ResponseEntity<?> fetchData(@RequestParam String apiUrl) {
        // Validate the API URL
        if (!isValidUrl(apiUrl)) {
            return ResponseEntity.status(HttpStatus.BAD_REQUEST).body("Invalid URL");
        }

        // Fetch data from external API with validation
        RestTemplate restTemplate = new RestTemplate();
        String response;
        try {
            response = restTemplate.getForObject(apiUrl, String.class);
        } catch (RestClientException e) {
            return ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR).body("Error fetching data");
        }

        return ResponseEntity.ok(response);
    }

    private boolean isValidUrl(String url) {
        // Implement URL validation logic
        return url.startsWith("https://trusted.com");
    }
}

The secure implementation:

  • Validates the API URL: Ensures that the URL is from a trusted source before making the request.

  • Handles errors gracefully: Catches exceptions and returns appropriate HTTP status codes to the client.

Key Points for Developers

  • Validate External API URLs: Ensure that external API URLs are from trusted sources before making requests.

  • Implement Proper Error Handling: Catch and handle exceptions to prevent exposure to malicious data.

  • Use Secure Communication: Use HTTPS for secure communication with external APIs.

  • Monitor and Log API Requests: Keep track of API requests and responses to detect any abnormal activities.

Summary and Key Takeaways

Unsafe Consumption of APIs can lead to significant security risks, including data breaches and exposure to malicious data. By validating external API URLs, implementing proper error handling, and using secure communication, developers can mitigate these risks and ensure the security of their applications.

Reference Links

PreviousBroken Function Level AuthorizationNextJAVA Exception Handling

Last updated 6 months ago

Was this helpful?

OWASP API Security Top 10:

Spring Security Documentation:

Spring Data JPA Documentation:

RestTemplate Documentation:

OWASP API Security Top 10
Spring Security Documentation
Spring Data JPA Documentation
Spring RestTemplate Documentation