Cross Origin Resource Sharing Implemented With Restricted Access

By
Rejah Rehim
Published on
02 Jul 2018
1 min read

Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional HTTP header to let the browser know that an application is running from one domain (Origin) and has permission to access resources from another origin (Server). The Cross-Origin Resource Sharing is not found in many of the servers. This vulnerability enables the web browser to perform cross-domain request using XMLHTTPRequest L2 API. There are many servers implemented with weak Cross-Origin Resource Sharing policy. The Cross-Origin Resource Sharing or CORS is a mechanism that enables a web browser to perform “cross-domain” requests using the XMLHttpRequest L2 API in a controlled manner. The content is visible via cross-origin resource sharing (CORS) files or headers this can lead to access to sensitive data.

Example

Consider a frontend script code for a web application served from http://example.beaglesecurity.com uses XMLHttpRequest to make a request for http://api.example.beaglesecurity.com/data.json.

Impact

The major impact includes code injection attacks. Code injection is the exploitation of a computer bug which includes processing invalid data.

Mitigation / Precaution

This vulnerability can be fixed:-

  • Implement the Cross-Origin Resource Sharing
Automated human-like penetration testing for your web apps & APIs
Teams using Beagle Security are set up in minutes, embrace release-based CI/CD security testing and save up to 65% with timely remediation of vulnerabilities. Sign up for a free account to see what it can do for you.

Written by
Rejah Rehim
Rejah Rehim
Co-founder, Director
Find website security issues in a flash
Improve your website's security posture with proactive vulnerability detection.
Free website security assessment
Experience the power of automated penetration testing & contextual reporting.