Skip to content

Disable decoupled destinations by default for WS-Addressing#3279

Merged
coheigea merged 1 commit into
mainfrom
coheigea/ws-addressing-decoupled-destinations
Jul 3, 2026
Merged

Disable decoupled destinations by default for WS-Addressing#3279
coheigea merged 1 commit into
mainfrom
coheigea/ws-addressing-decoupled-destinations

Conversation

@coheigea

@coheigea coheigea commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

(Non-anonymous) decoupled destinations represent an SSRF risk and are not needed for most WS-Addressing scenarios. This PR disables it by default and adds a system property to turn them on again. The flag only applies for WS-Addressing, as WS-RM relies on decoupled addresses we allow it there.

@coheigea coheigea force-pushed the coheigea/ws-addressing-decoupled-destinations branch from a56b06b to ce9f05d Compare July 3, 2026 09:58
@reta

reta commented Jul 3, 2026

Copy link
Copy Markdown
Member

Thanks @coheigea !

@coheigea coheigea force-pushed the coheigea/ws-addressing-decoupled-destinations branch from ce9f05d to 8d331bc Compare July 3, 2026 13:25
@coheigea coheigea force-pushed the coheigea/ws-addressing-decoupled-destinations branch from 8d331bc to 4d11441 Compare July 3, 2026 14:18
@coheigea coheigea merged commit 24a45ef into main Jul 3, 2026
5 checks passed
@coheigea coheigea deleted the coheigea/ws-addressing-decoupled-destinations branch July 3, 2026 15:29
coheigea added a commit that referenced this pull request Jul 3, 2026
coheigea added a commit that referenced this pull request Jul 3, 2026
ppalaga added a commit to ppalaga/quarkus-cxf that referenced this pull request Jul 6, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
@ppalaga

ppalaga commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Thanks for this fix, @coheigea. When testing with it I have found a small issue:

When setting decoupled.enabled=true and reducing allowedSchemes to just https:// via system property, the error message still says

Decoupled WS-Addressing ReplyTo (http://localhost:8081/ws-addressing-target/replyTo) is not permitted by this server. Enable with system property org.apache.cxf.ws.addressing.decoupled.enabled=true

That's misleading, because decoupled.enabled=true is set already. It should recommend to expand the allowedSchemes.

Besides that, as usual, I would like to let Quarkus CXF users to use MicroProfile config to configure the decoupled permissions. Implementing it is easy, the only question is, whether we could find a way for Quarkus CXF to override the error and log messages to use quarkus.cxf.endpoint.addressing.decoupled.enabled and quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes instead of org.apache.cxf.ws.addressing.decoupled.enabled and org.apache.cxf.ws.addressing.decoupled.allowedSchemes respectively? An SPI would perhaps work, but it sounds like an overkill for such a simple thing. Could we perhaps introduce some system properties for that?

I'd be happy to send a PR for both issues in case it sounds reasonable to you?

ppalaga added a commit to ppalaga/quarkus-cxf that referenced this pull request Jul 6, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
ppalaga added a commit to quarkiverse/quarkus-cxf that referenced this pull request Jul 7, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
@coheigea

coheigea commented Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

@ppalaga Thanks for taking a look, please submit a PR for the misleading error message. For the Quarkus proposal, do we have an existing template for this for other configuration properties?

ppalaga added a commit to ppalaga/quarkus-cxf that referenced this pull request Jul 8, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
@ppalaga

ppalaga commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

@ppalaga Thanks for taking a look, please submit a PR for the misleading error message. For the Quarkus proposal, do we have an existing template for this for other configuration properties?

Thanks, @coheigea, this PR #3300 covers both:

  • Adds ,or set ...allowedSchemes to the log or fault messages where needed
  • Puts the messages into a resource bundle, which allows us to override them using some class loading trickery on Quarkus CXF.

ppalaga added a commit to quarkiverse/quarkus-cxf that referenced this pull request Jul 10, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
ppalaga added a commit to quarkiverse/quarkus-cxf that referenced this pull request Jul 10, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
ppalaga added a commit to quarkiverse/quarkus-cxf that referenced this pull request Jul 10, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
ppalaga added a commit to quarkiverse/quarkus-cxf that referenced this pull request Jul 10, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
ppalaga added a commit to quarkiverse/quarkus-cxf that referenced this pull request Jul 10, 2026
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration
parameters to make Quarkus CXF work with the changes in
apache/cxf#3279
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants