ghsa-w5m2-299g-rff5
Vulnerability from github
Published
2022-04-26 12:59
Modified
2022-04-26 12:59
Summary
Page Compare Reflected Cross-site Scripting (XSS) vulnerability
Details

Impact

ACS Commons version 5.1.x (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in /apps/acs-commons/content/page-compare.html endpoint via the a and b GET parameters. User input submitted via these parameters is not validated or sanitized.

An attacker must provide a link to someone with access to AEM Author, and could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. The exploitation of this issue requires user interaction in order to be successful.

Patches

This issue has been resolved in 5.2.0.

Workarounds

None

References

N/A

For more information

If you have any questions or comments about this advisory open an issue in acs-aem-commons.

Credit

This issue was discovered and reported by Black Lantern Security.

https://hackerone.com/reports/1466020

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "com.adobe.acs:acs-aem-commons"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.2.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-28820"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-04-26T12:59:00Z",
    "nvd_published_at": "2022-04-21T19:15:00Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nACS Commons version 5.1.x (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in `/apps/acs-commons/content/page-compare.html` endpoint via the `a` and `b` GET parameters. User input submitted via these parameters is not validated or sanitized.\n\nAn attacker must provide a link to someone with access to AEM Author, and could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim\u0027s browser. The exploitation of this issue requires user interaction in order to be successful.\n\n### Patches\n\nThis issue has been resolved in 5.2.0.\n\n### Workarounds\n\nNone \n\n### References\n\nN/A\n\n### For more information\n\nIf you have any questions or comments about this advisory open an issue in acs-aem-commons.\n\n### Credit\n\nThis issue was discovered and reported by Black Lantern Security.\n\nhttps://hackerone.com/reports/1466020",
  "id": "GHSA-w5m2-299g-rff5",
  "modified": "2022-04-26T12:59:00Z",
  "published": "2022-04-26T12:59:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/Adobe-Consulting-Services/acs-aem-commons/security/advisories/GHSA-w5m2-299g-rff5"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-28820"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/Adobe-Consulting-Services/acs-aem-commons"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Page Compare Reflected Cross-site Scripting (XSS) vulnerability"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading...

Loading...

Loading...
  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.