Closed Bug 1365661 Opened 8 years ago Closed 8 years ago

blog.mozilla.com allows access to /wp-json and /wp-admin

Categories

(Infrastructure & Operations :: Blogs, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sakshyam.shah, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: reporter-external, Whiteboard: [reporter-external] [web-bounty-form] [verif?])

Admins responsible for hosting blog at blog.mozilla.com has so far done great job in hiding version numbers and default wordpress pages. But url at https://blog.mozilla.org/wp-json returns json schema specific to blog.mozilla.com which further reveals unnecessary informations which might aid malicious user to enumerate user with user id via url https://blog.mozilla.org/wp-json/wp/v2/users/ , identify allowed HTTP schema and methods via url https://blog.mozilla.org/wp-json/wp/v2/ and so on. While this currently does not reveal any sensitive informations, it is better to hide this from public/unauthenticated user which might aid attacker in case of other attack vectors. you can visit following url to verify the issue: https://blog.mozilla.org/wp-json https://blog.mozilla.org/wp-json/wp/v2/users/ https://blog.mozilla.org/wp-json/wp/v2/
Flags: sec-bounty?
sakshyam: thanks for your report, but this is known behavior and we consider it as public information.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Group: websites-security
Flags: sec-bounty? → sec-bounty-
Component: Other → WebOps: Blogs
Product: Websites → Infrastructure & Operations
Summary: exposed json schema to unauthenticated user in blog.mozilla.com at url https://blog.mozilla.org/wp-json seems like unnecessary information disclosure → blog.mozilla.com allows access to /wp-json and /wp-admin
Duplicate of this bug: 1823465
Duplicate of this bug: 1829458
Blocks: 1830029
Duplicate of this bug: 1836070
Duplicate of this bug: 1849917
Duplicate of this bug: 1868518
You need to log in before you can comment on or make changes to this bug.