ghsa-265r-pp83-gww7
Vulnerability from github
Published
2022-05-24 17:09
Modified
2022-11-03 23:46
Summary
Cross-site Scripting in Apache Struts
Details

When the Struts2 debug mode is turned on, under certain conditions an arbitrary script may be executed in the 'Problem Report' screen. Also if JSP files are exposed to be accessed directly it's possible to execute an arbitrary script.

It is generally not advisable to have debug mode switched on outside of the development environment. Debug mode should always be turned off in production setup. Also never expose JSPs files directly and hide them inside WEB-INF folder or define dedicated security constraints to block access to raw JSP files.

Struts >= 2.3.20 is not vulnerable to this attack. We recommend upgrading to Struts 2.3.20 or higher if turning off debug mode is not possible.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.struts:struts2-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.3.20",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2015-2992",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-79",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-11-03T23:46:11Z",
      nvd_published_at: "2020-02-27T18:15:00Z",
      severity: "MODERATE",
   },
   details: "When the Struts2 debug mode is turned on, under certain conditions an arbitrary script may be executed in the 'Problem Report' screen. Also if JSP files are exposed to be accessed directly it's possible to execute an arbitrary script. \n\nIt is generally not advisable to have debug mode switched on outside of the development environment. Debug mode should always be turned off in production setup. Also never expose JSPs files directly and hide them inside WEB-INF folder or define dedicated security constraints to block access to raw JSP files.\n\nStruts >= 2.3.20 is not vulnerable to this attack. We recommend upgrading to Struts 2.3.20 or higher if turning off debug mode is not possible.",
   id: "GHSA-265r-pp83-gww7",
   modified: "2022-11-03T23:46:11Z",
   published: "2022-05-24T17:09:44Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2015-2992",
      },
      {
         type: "WEB",
         url: "https://cwiki.apache.org/confluence/display/WW/S2-025",
      },
      {
         type: "WEB",
         url: "https://cwiki.apache.org/confluence/display/WW/Security",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/apache/struts",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20200330-0001",
      },
      {
         type: "WEB",
         url: "http://jvn.jp/en/jp/JVN88408929/index.html",
      },
      {
         type: "WEB",
         url: "http://jvndb.jvn.jp/en/contents/2015/JVNDB-2015-000124.html",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/76624",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
   summary: "Cross-site Scripting in Apache Struts",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

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