Google Chrome OS 25.0.1364.173 .pangorc pango-utils.c environment link following
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Google Chrome OS 25.0.1364.173. The impacted element is an unknown function of the file pango-utils.c of the component .pangorc. Executing a manipulation of the argument environment can lead to link following. This vulnerability is tracked as CVE-2013-0927. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Google Chrome OS 25.0.1364.173 (Web Browser). It has been declared as critical. This vulnerability affects an unknown functionality of the file pango-utils.c of the component .pangorc. The manipulation of the argument environment with an unknown input leads to a link following vulnerability. The CWE definition for the vulnerability is CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Google Chrome OS before 26.0.1410.57 relies on a Pango pango-utils.c read_config implementation that loads the contents of the .pangorc file in the user s home directory, and the file referenced by the PANGO_RC_FILE environment variable, which allows attackers to bypass intended access restrictions via crafted configuration data.
The weakness was disclosed 04/08/2013 by Pinkie Pie as not defined changelog entry (Website). The advisory is available at googlechromereleases.blogspot.ch. The public release has been coordinated in cooperation with the vendor. This vulnerability was named CVE-2013-0927 since 01/07/2013. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/05/2018). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 26.0.1410.57 eliminates this vulnerability. The upgrade is hosted for download at git.chromium.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.chromium.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (92256†). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Link followingCWE: CWE-59
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chrome OS 26.0.1410.57
Patch: git.chromium.org
Timeline
01/07/2013 🔍04/08/2013 🔍
04/08/2013 🔍
04/10/2013 🔍
04/17/2013 🔍
05/05/2018 🔍
Sources
Vendor: google.comAdvisory: googlechromereleases.blogspot.ch
Researcher: Pinkie Pie
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2013-0927 (🔍)
GCVE (CVE): GCVE-0-2013-0927
GCVE (VulDB): GCVE-100-8422
OSVDB: 92256
Entry
Created: 04/17/2013 17:39Updated: 05/05/2018 18:05
Changes: 04/17/2013 17:39 (56), 05/05/2018 18:05 (6)
Complete: 🔍
Committer:
Cache ID: 216:5DF:103
No comments yet. Languages: en.
Please log in to comment.