| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in GPhotos. This issue affects some unknown processing of the file affich.php. The manipulation of the argument image leads to cross site scripting. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in GPhotos (affected version unknown). This issue affects an unknown functionality of the file affich.php. The manipulation of the argument image with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is integrity.
The weakness was published 05/13/2006 by Moroccan Security (Website). The advisory is shared at archives.neohapsis.com. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
After before and not just, there has been an exploit disclosed. The exploit is available at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:affich.php 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 SecurityFocus (BID 17967†), OSVDB (25499†) and Secunia (SA20095†). Similar entries are available at VDB-30252, VDB-30251 and VDB-83944. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.3
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: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/13/2006 🔍05/13/2006 🔍
05/13/2006 🔍
05/15/2006 🔍
05/15/2006 🔍
05/08/2016 🔍
12/02/2018 🔍
Sources
Advisory: archives.neohapsis.comResearcher: Moroccan Security
Status: Not defined
GCVE (VulDB): GCVE-100-83945
SecurityFocus: 17967 - Gphotos Multiple Input Validation Vulnerabilities
Secunia: 20095 - GPhotos Cross-Site Scripting and Disclosure of Arbitrary Directories, Less Critical
OSVDB: 25499 - GPhotos affich.php image Parameter XSS
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/08/2016 19:40Updated: 12/02/2018 09:53
Changes: 05/08/2016 19:40 (50), 12/02/2018 09:53 (2)
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.