ASP-Nuke 0.80 Web Cache language_select.asp LangCode authentication spoofing
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in ASP-Nuke 0.80. This impacts an unknown function of the file language_select.asp of the component Web Cache. Performing a manipulation of the argument LangCode results in authentication spoofing. This vulnerability is reported as CVE-2005-2065. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, was found in ASP-Nuke 0.80. This affects an unknown code of the file language_select.asp of the component Web Cache. The manipulation of the argument LangCode with an unknown input leads to a authentication spoofing vulnerability. CWE is classifying the issue as CWE-290. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. This is going to have an impact on integrity. The summary by CVE is:
HTTP response splitting vulnerability in language_select.asp in ASP Nuke 0.80 allows remote attackers to spoof web content and poison web caches via CRLF ("%0d%0a") sequences in the LangCode parameter.
The weakness was disclosed 06/29/2005 by Alberto Trivero (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is uniquely identified as CVE-2005-2065 since 06/29/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:language_select.asp it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Exploit-DB (25907) and SecurityFocus (BID 14063†). The entries VDB-25618 and VDB-25616 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Authentication spoofingCWE: CWE-290 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/27/2005 🔍06/29/2005 🔍
06/29/2005 🔍
06/29/2005 🔍
03/11/2015 🔍
06/27/2024 🔍
Sources
Advisory: marc.theaimsgroup.comResearcher: Alberto Trivero
Status: Not defined
CVE: CVE-2005-2065 (🔍)
GCVE (CVE): GCVE-0-2005-2065
GCVE (VulDB): GCVE-100-25617
SecurityFocus: 14063 - ASPNuke Language_Select.ASP HTTP Response Splitting Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/11/2015 11:41Updated: 06/27/2024 14:43
Changes: 03/11/2015 11:41 (46), 07/09/2018 09:07 (7), 06/27/2024 14:43 (25)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.