ghsa-j2hg-w4p4-6rvm
Vulnerability from github
Published
2022-05-17 04:54
Modified
2024-06-11 19:29
Severity ?
Summary
EC-CUBE vulnerable to authorization bypass
Details
Authorization bypass through user-controlled key issue exists in EC-CUBE 2.11.0 through 2.12.2 and EC-Orange systems deployed before June 29th, 2015. If this vulnerability is exploited, a user of the affected shopping website may obtain other users' information by sending a crafted HTTP request.
{ affected: [ { package: { ecosystem: "Packagist", name: "ec-cube/ec-cube", }, ranges: [ { events: [ { introduced: "2.11.0", }, { fixed: "2.12.2", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2014-0808", ], database_specific: { cwe_ids: [ "CWE-639", ], github_reviewed: true, github_reviewed_at: "2024-06-11T19:29:36Z", nvd_published_at: "2014-01-22T21:55:00Z", severity: "MODERATE", }, details: "Authorization bypass through user-controlled key issue exists in EC-CUBE 2.11.0 through 2.12.2 and EC-Orange systems deployed before June 29th, 2015. If this vulnerability is exploited, a user of the affected shopping website may obtain other users' information by sending a crafted HTTP request.", id: "GHSA-j2hg-w4p4-6rvm", modified: "2024-06-11T19:29:36Z", published: "2022-05-17T04:54:13Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2014-0808", }, { type: "PACKAGE", url: "https://github.com/EC-CUBE/ec-cube", }, { type: "WEB", url: "https://jvn.jp/en/jp/JVN15637138", }, { type: "WEB", url: "https://jvndb.jvn.jp/jvndb/JVNDB-2024-000054", }, { type: "WEB", url: "http://jvn.jp/en/jp/JVN51770585", }, { type: "WEB", url: "http://jvn.jp/en/jp/JVN51770585/index.html", }, { type: "WEB", url: "http://jvndb.jvn.jp/jvndb/JVNDB-2014-000006", }, { type: "WEB", url: "http://www.ec-cube.net/info/weakness/weakness.php?id=57", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", type: "CVSS_V3", }, ], summary: "EC-CUBE vulnerable to authorization bypass", }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.