| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Umbraco 4.7.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file FeedProxy.aspx. Performing a manipulation of the argument url results in input validation. This vulnerability is identified as CVE-2012-1301. The attack can be initiated remotely. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in Umbraco 4.7.0. It has been classified as critical. This affects an unknown function of the file FeedProxy.aspx. The manipulation of the argument url with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The FeedProxy.aspx script in Umbraco 4.7.0 allows remote attackers to proxy requests on their behalf via the "url" parameter.
The bug was discovered 01/26/2012. The weakness was released 04/13/2017 by Florent Daigniere as not defined posting (Bugtraq). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2012-1301 since 02/27/2012. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 1904 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:FeedProxy.aspx it is possible to find vulnerable targets with Google Hacking.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at SecurityFocus (BID 52912†) and OSVDB (80963†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
01/26/2012 🔍02/27/2012 🔍
04/05/2012 🔍
04/13/2017 🔍
04/13/2017 🔍
04/14/2017 🔍
08/30/2020 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Florent Daigniere
Status: Not defined
CVE: CVE-2012-1301 (🔍)
GCVE (CVE): GCVE-0-2012-1301
GCVE (VulDB): GCVE-100-99771
SecurityFocus: 52912 - Umbraco CMS 'url' Parameter Open Proxy Vulnerability
OSVDB: 80963 - CVE-2012-1301 - Umbraco - Open Proxy Issue
Entry
Created: 04/14/2017 10:50Updated: 08/30/2020 09:39
Changes: 04/14/2017 10:50 (65), 08/30/2020 09:39 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.