Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #41858 XSS via the tracker names used in the semantic timeframe deletion message
    Actions
    Infos
    #41858
    Thomas Gerbet (tgerbet)
    2025-03-03 09:32
    2025-02-20 16:26
    43526
    Details
    XSS via the tracker names used in the semantic timeframe deletion message

    The message explaining why a specific field cannot be removed when used by a semantic can contain unescaped information.

    Impact

    A tracker administrator with a semantic timeframe used by other trackers could use this vulnerability to force other tracker administrators to execute uncontrolled code.

    CVSSv3.1 score: 4.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:L)

    Exploitation

    In 2 trackers have a semantic timeframe with one inherited from the other.
    Rename the "source" tracker to something like "><script>alert(1)</script>, open the field administration of the other tracker.

    References

    CWE 79
    OWASP Cross-site Scripting
    CVE-2025-27099

    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2025-02-20
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #41091 Tuleap Releases 16.5 Delivered 2025-02-27 11:44 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #41858

    Git commit

    tuleap/tuleap/stable

    fix: request #41858 XSS via the tracker names used in the semantic timeframe deletion message bec10bd5c9
    User avatar Thomas Gerbet (tgerbet) , 2025-02-20 16:31
    Merge commit 'refs/changes/66/33566/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 5560b054c3
    User avatar Marie Ange Garnier (marieange) , 2025-02-20 17:11
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2025-02-21 09:11

    CVE-2025-27099 has been assigned to this issue.

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes