apache / apache/pulsar

[Bug] Disable HTTP TRACE Method in webservice

Open
#18,091 1 comment 0 reactions 0 assignees View on GitHub
Stale type/bug
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Version

master

### Minimal reproduce step

Pulsar uses embedded jetty which allows TRACE method by default. This is a widely-known security concern. Please disable HTTP TRACE method.

### What did you expect to see?

https://issues.apache.org/jira/browse/ZOOKEEPER-3731

### What did you see instead?

https://issues.apache.org/jira/browse/ZOOKEEPER-3731

### Anything else?

https://github.com/apache/zookeeper/commit/44de549657a539dcedba58d56e67b8c906c89580

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start by tracing Pulsar's embedded Jetty webservice configuration and review the linked ZooKeeper commit for the relevant approach. Done means HTTP TRACE is disabled in the affected webservice while other HTTP methods continue to work; add or run the applicable webservice tests if the configuration points to them.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.