GCVE-1988-2026-0550

Vulnerability from gna-1988 – Published: 2026-11-05 04:38 – Updated: 2026-11-05 04:38
VLAI
Title
Apache Struts2 Tiles Plugin <=7.4.0 and >=6.3.0 Preparer Cache Vulnerabilities
Summary
The Apache Struts2 Tiles plugin version <=7.4.0 (and >=6.3.0) codebase includes a `ViewPreparer` construct, replete with multiple ViewPreparer factories, that contains several important vulnerabilities including unsynchronised, unbounded caches. The lack of proper synchronisation means that certain factories will create caches that race, risking lost cache entries, corrupted internal bucket states under load (this can result in infinite loops that consume large amounts of compute or time, among other things), expensive duplicate `put(Object, Object)` calls, and similar issues. The lack of an eviction process means that the cache can grow to arbitrary lengths, consume excessive amounts of memory, especially since the information system fails to utilise a starting size. These problems are compounded by the cache being `protected`, directly exposing it across the package and any inheriting classes, as well as attackers being able to control the key (if, for example, the cache is dynamically managed and attackers can set part of the key or leveraging the vulnerability discussed in `Apache Struts2 Core Arbitrary Code Execution via OGNL Sandbox Escape` (01 November 2026) to call to create preparers, call to getPreparer, etc.). Importantly, this file appears to have come from an older, known vulnerable, known buggy version of Tiles that was placed into the Apache Struts2 codebase, instead of the Tiles 3 version, when the Apaches Tiles project was retired and archived into the Apache Attic and, as such, when the Apache Struts2 maintainers decided to import at least a subset of the Tiles codebase into their own. By sucking in the buggy version, however, the Apache Struts2 Tiles plugin contained within said codebase inherits all issues that the imported code contained. Examples BasicPreparerFactory Race and Lack of an Eviction Process The Apache Struts2 Tiles container is initialised as an application-scoped singleton resource. Each request to the server utilises a separate thread, with each thread having access to the Tiles singleton. If the requests execute Tiles definitions that require view preparers, they will simultaneously invoke the factory instance being used, so it is important that the factory utilise thread-safe constructs. The `BasicPreparerFactory`, which is the default Tiles `ViewPreparer` factory, however, leverages an unsynchronised `HashMap` keyed by the preparer name. At issue are a couple of things. First, there is a time-of-check, time-of-use (TOCTOU) race condition in `getPreparer(String, Request)` -- this requires a proper lock or an atomic/locking call or, in a multi-threaded context, which is what happens in a Tiles workflow, it is prone to racing. Second, there simply isn't a limit to the size of the Map and the default capacity is used. This was the original design of Tiles and was a known issue, which manifested itself in denial of service (DoS) conditions in certain use cases, but was generally "mitigated" by having Tiles initialised and setup as part of the server start up routine (although plenty of systems still leveraged a more dynamic approach) -- the service would read the tiles configuration at start up, create and stuff the cache then, using a serial process. This design, however, was still suboptimal, buggy, and problematic, even when used in that way, resulting in several overhauls and, eventually, settling in Tiles 3. The old process, regardless, was suboptimal even from the most basic of perspectives -- since it was a one-time, start-up cost (typically -- again, developers and the like were free to, and often did, perform dynamic building), there was little reason to utilise the default capacity -- the desired size and capacity was trivially calculable and known, so it could and should have been set thereto to prevent excessive memory use, with a better-tuned automatic resizing threshold. That, of course, however, was the least of the problems, which is why Tiles 3 shifted to a `ConcurrentHashMap` (realistically, a sub-optimal solution, as it is generally best to control your own resources since such structures can still race via TOCTOU -- e.g., ` if (!map.containsKey(key)) map.put(key, value);`-- and similar coding constructs). ```java /** * Maps a preparer name to the instantiated preparer. */ protected Map<String, ViewPreparer> preparers; /** * Constructor. */ public BasicPreparerFactory() { this.preparers = new HashMap<>(); } /** * Create a new instance of the named preparerInstance. This factory * expects all names to be qualified class names. * * @param name the named preparerInstance * @param context current context * @return ViewPreparer instance */ public ViewPreparer getPreparer(String name, Request context) { if (!preparers.containsKey(name)) { preparers.put(name, createPreparer(name)); } return preparers.get(name); } ``` Code snippet from struts2-tiles-plugin's plugins/tiles/src/main/java/org/apache/tiles/core/prepare/factory/BasicPreparerFactory.java, lines 44-71 _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Apache Struts2 Tiles Affected: unknown
guessed Create a notification for this product.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "Struts2 Tiles",
          "vendor": "Apache",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Daniel Owens via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "The Apache Struts2 Tiles plugin version \u003c=7.4.0 (and \u003e=6.3.0) codebase includes a `ViewPreparer` construct, replete \nwith multiple ViewPreparer factories, that contains several important vulnerabilities including unsynchronised, \nunbounded caches.  The lack of proper synchronisation means that certain factories will create caches that race, \nrisking lost cache entries, corrupted internal bucket states under load (this can result in infinite loops that consume \nlarge amounts of compute or time, among other things), expensive duplicate `put(Object, Object)` calls, and similar \nissues.  The lack of an eviction process means that the cache can grow to arbitrary lengths, consume excessive amounts \nof memory, especially since the information system fails to utilise a starting size.  These problems are compounded by \nthe cache being `protected`, directly exposing it across the package and any inheriting classes, as well as attackers \nbeing able to control the key (if, for example, the cache is dynamically managed and attackers can set part of the key \nor leveraging the vulnerability discussed in `Apache Struts2 Core Arbitrary Code Execution via OGNL Sandbox Escape` (01 \nNovember 2026) to call to create preparers, call to getPreparer, etc.).\n\nImportantly, this file appears to have come from an older, known vulnerable, known buggy version of Tiles that was \nplaced into the Apache Struts2 codebase, instead of the Tiles 3 version, when the Apaches Tiles project was retired and \narchived into the Apache Attic and, as such, when the Apache Struts2 maintainers decided to import at least a subset of \nthe Tiles codebase into their own.  By sucking in the buggy version, however, the Apache Struts2 Tiles plugin contained \nwithin said codebase inherits all issues that the imported code contained.\n\nExamples\nBasicPreparerFactory Race and Lack of an Eviction Process\nThe Apache Struts2 Tiles container is initialised as an application-scoped singleton resource.  Each request to the \nserver utilises a separate thread, with each thread having access to the Tiles singleton.  If the requests execute \nTiles definitions that require view preparers, they will simultaneously invoke the factory instance being used, so it \nis important that the factory utilise thread-safe constructs.  The `BasicPreparerFactory`, which is the default Tiles \n`ViewPreparer` factory, however, leverages an unsynchronised `HashMap` keyed by the preparer name.\n\nAt issue are a couple of things.  First, there is a time-of-check, time-of-use (TOCTOU) race condition in \n`getPreparer(String, Request)` -- this requires a proper lock or an atomic/locking call or, in a multi-threaded \ncontext, which is what happens in a Tiles workflow, it is prone to racing.  Second, there simply isn\u0027t a limit to the \nsize of the Map and the default capacity is used.\n\nThis was the original design of Tiles and was a known issue, which manifested itself in denial of service (DoS) \nconditions in certain use cases, but was generally \"mitigated\" by having Tiles initialised and setup as part of the \nserver start up routine (although plenty of systems still leveraged a more dynamic approach) -- the service would read \nthe tiles configuration at start up, create and stuff the cache then, using a serial process.  This design, however, \nwas still suboptimal, buggy, and problematic, even when used in that way, resulting in several overhauls and, \neventually, settling in Tiles 3.  The old process, regardless, was suboptimal even from the most basic of perspectives \n-- since it was a one-time, start-up cost (typically -- again, developers and the like were free to, and often did, \nperform dynamic building), there was little reason to utilise the default capacity -- the desired size and capacity was \ntrivially calculable and known, so it could and should have been set thereto to prevent excessive memory use, with a \nbetter-tuned automatic resizing threshold.  That, of course, however, was the least of the problems, which is why Tiles \n3 shifted to a `ConcurrentHashMap` (realistically, a sub-optimal solution, as it is generally best to control your own \nresources since such structures can still race via TOCTOU -- e.g., ` if (!map.containsKey(key)) map.put(key, value);`-- \nand similar coding constructs).\n\n```java\n    /**\n     * Maps a preparer name to the instantiated preparer.\n     */\n    protected Map\u003cString, ViewPreparer\u003e preparers;\n\n    /**\n     * Constructor.\n     */\n    public BasicPreparerFactory() {\n        this.preparers = new HashMap\u003c\u003e();\n    }\n\n\n    /**\n     * Create a new instance of the named preparerInstance.  This factory\n     * expects all names to be qualified class names.\n     *\n     * @param name    the named preparerInstance\n     * @param context current context\n     * @return ViewPreparer instance\n     */\n    public ViewPreparer getPreparer(String name, Request context) {\n        if (!preparers.containsKey(name)) {\n            preparers.put(name, createPreparer(name));\n        }\n\n        return preparers.get(name);\n    }\n```\nCode snippet from struts2-tiles-plugin\u0027s \nplugins/tiles/src/main/java/org/apache/tiles/core/prepare/factory/BasicPreparerFactory.java, lines 44-71\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-05T04:38:41Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/11"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/11"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/11"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Apache Struts2 Tiles Plugin \u003c=7.4.0 and \u003e=6.3.0 Preparer Cache Vulnerabilities",
      "x_gcve": [
        {
          "recordType": "advisory",
          "relationships": [],
          "vulnId": "GCVE-1988-2026-0550",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/11",
            "automated": true,
            "contentSha256": "e8432a683aeda22d01098e3ea45ce46c2400d83f876dcd5779f3204168bcbe70",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/11",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-04T22:34:51Z"
          }
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-05T04:38:41Z",
    "dateUpdated": "2026-11-05T04:38:41Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0550"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.