GithubHelp home page GithubHelp logo

Comments (8)

k8s-ci-robot avatar k8s-ci-robot commented on June 4, 2024

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

from ingress-nginx.

longwuyuan avatar longwuyuan commented on June 4, 2024

How can a reader test or reproduce the XSS

from ingress-nginx.

smaniraju avatar smaniraju commented on June 4, 2024

This issue is reported in static code analysis tools.
The root cause issue is data directly read from connection (tcp.go:65) is being written back pkg/tcpproxy/tcp.go:110 which leads to XSS issues.

from ingress-nginx.

rikatz avatar rikatz commented on June 4, 2024

sorry, what static code analysis? How was this detected?

Without a way to reproduce, we cannot accept this issue.

/triage needs-information

from ingress-nginx.

longwuyuan avatar longwuyuan commented on June 4, 2024

/remove-kind bug

from ingress-nginx.

smaniraju avatar smaniraju commented on June 4, 2024

static-code analysis tools like fortify.

from ingress-nginx.

rikatz avatar rikatz commented on June 4, 2024

Sorry, without a proper report and some more information it is not easy to reproduce.

Also this part of the code does tcp stream directly, it is not even related with l7/http proxying so I'm curious how this was identified.

At this point I am closing this issue, if you have some more information, some real report, etc please let me know! Thanks

/close

from ingress-nginx.

k8s-ci-robot avatar k8s-ci-robot commented on June 4, 2024

@rikatz: Closing this issue.

In response to this:

Sorry, without a proper report and some more information it is not easy to reproduce.

Also this part of the code does tcp stream directly, it is not even related with l7/http proxying so I'm curious how this was identified.

At this point I am closing this issue, if you have some more information, some real report, etc please let me know! Thanks

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

from ingress-nginx.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.