GHSA-5Q7Q-QQW2-HJQ7
Vulnerability from github – Published: 2022-01-06 18:32 – Updated: 2022-08-11 18:44Overview
Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary JavaScript objects.
Description
Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it.
XSS effects vary in range from petty nuisance to significant security risk, depending on the sensitivity of the data handled by the vulnerable site and the nature of any security mitigation implemented by the site's owner network.
Releases
Releases before version 21.12.22.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.
Workarounds
A workaround exists that replaces one of the core JavaScript files embedded in the library. Using a XML configuration allows to replace the default JavaScript code to be replaced with the version on GitHub.
<configuration>
<configSections>
<sectionGroup name="ajaxNet">
<section name="ajaxSettings" type="AjaxPro.AjaxSettingsSectionHandler,AjaxPro.2" requirePermission="false" restartOnExternalChanges="true"/>
</sectionGroup>
</configSections>
<ajaxNet>
<ajaxSettings>
<coreScript>~/ajaxpro-core-fixed.js</coreScript>
</ajaxSettings>
</ajaxNet>
</configuration>
Copy the file core.js from the main project folder to your web server root folder and rename that ajaxpro-core-fixed.js.
Clients need to refresh the web page to download the changed JavaScript code.
References
Commit fixing the issue: c89e39b9679fcb8ab6644fe21cc7e652cb615e2b
Note: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/
For more information
If you have any questions or comments about this advisory: * Open an issue on this GitHub repository
{
"affected": [
{
"package": {
"ecosystem": "NuGet",
"name": "AjaxNetProfessional"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "21.12.22.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-43853"
],
"database_specific": {
"cwe_ids": [
"CWE-502",
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2022-01-04T21:21:17Z",
"nvd_published_at": "2021-12-22T21:15:00Z",
"severity": "HIGH"
},
"details": "### Overview\n\nAffected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary JavaScript objects.\n\n### Description\n\nCross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it.\n\nXSS effects vary in range from petty nuisance to significant security risk, depending on the sensitivity of the data handled by the vulnerable site and the nature of any security mitigation implemented by the site\u0027s owner network.\n\n### Releases\n\nReleases before version 21.12.22.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.\n\n### Workarounds\n\nA workaround exists that replaces one of the core JavaScript files embedded in the library. Using a XML configuration allows to replace the default JavaScript code to be replaced with the version on GitHub.\n\n```xml\n\u003cconfiguration\u003e\n\t\u003cconfigSections\u003e\n\t\t\u003csectionGroup name=\"ajaxNet\"\u003e\n\t\t\t\u003csection name=\"ajaxSettings\" type=\"AjaxPro.AjaxSettingsSectionHandler,AjaxPro.2\" requirePermission=\"false\" restartOnExternalChanges=\"true\"/\u003e\n\t\t\u003c/sectionGroup\u003e\n\t\u003c/configSections\u003e\n\t\u003cajaxNet\u003e\n\t\t\u003cajaxSettings\u003e\n\t\t\t\u003ccoreScript\u003e~/ajaxpro-core-fixed.js\u003c/coreScript\u003e\n\t\t\u003c/ajaxSettings\u003e\n\t\u003c/ajaxNet\u003e\n\u003c/configuration\u003e\n```\n\nCopy the file core.js from the main project folder to your web server root folder and rename that ajaxpro-core-fixed.js.\n\nClients need to refresh the web page to download the changed JavaScript code.\n\n### References\n\nCommit fixing the issue: c89e39b9679fcb8ab6644fe21cc7e652cb615e2b\n\nNote: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on this GitHub repository\n",
"id": "GHSA-5q7q-qqw2-hjq7",
"modified": "2022-08-11T18:44:32Z",
"published": "2022-01-06T18:32:24Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/michaelschwarz/Ajax.NET-Professional/security/advisories/GHSA-5q7q-qqw2-hjq7"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43853"
},
{
"type": "WEB",
"url": "https://github.com/michaelschwarz/Ajax.NET-Professional/commit/c89e39b9679fcb8ab6644fe21cc7e652cb615e2b"
},
{
"type": "PACKAGE",
"url": "https://github.com/michaelschwarz/Ajax.NET-Professional"
},
{
"type": "WEB",
"url": "https://github.com/michaelschwarz/Ajax.NET-Professional/releases/tag/v21.12.22.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "AjaxNetProfessional deserializes arbitrary JavaScript objects"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.