# Build a Better Panel
**Category**: Web \**Points**: 299 (13 solves) \**Author**: Jim
## Challenge
BAP wasn't secure enough. Now the admin is a bit smarter, see if you can stillget the flag! If you experience any issues, send it[here](https://us-east1-dicegang.cloudfunctions.net/ctf-2021-admin-bot?challenge=build-a-better-panel)
NOTE: The admin will only visit sites that match the following regex`^https:\/\/build-a-better-panel\.dicec\.tf\/create\?[0-9a-z\-\=]+$`
Site: [build-a-better-panel.dicec.tf](build-a-better-panel.dicec.tf) \Attachments: `build-a-better-panel.tar.gz`
## Solution
Solved with ath0.
This is nearly identically to [Build a Panel](../build_a_panel) except:- The `panelId` cookie is `sameSite: 'strict'` instead of `'lax'`- The admin bot only goes to `/create`
Instead of directly giving the admin bot a URL that triggers SQL injection, wehave to make a `/create` page that requests that URL.
Looking at the `/create` route we have:```javascriptapp.get('/create', (req, res) => {    const cookies = req.cookies;    const queryParams = req.query;
    if(!cookies['panelId']){        const newPanelId = queryParams['debugid'] || uuidv4();        console.log(newPanelId);
        res.cookie('panelId', newPanelId, {maxage: 10800, httponly: true, sameSite: 'lax'});    }
    res.redirect('/panel/');});```
We can specify a `debugid` so that the admin bot goes to a specific panel.
Now we have to craft a panel that sends the SQL injection request.For reference, this is what a default panel looks like:
![panel.png](panel.png)
Looking at `app/public/cusotm.js`, we see a prototype pollution vulnerability here:```javascriptconst mergableTypes = ['boolean', 'string', 'number', 'bigint', 'symbol', 'undefined'];
const safeDeepMerge = (target, source) => {    for (const key in source) {        if(!mergableTypes.includes(typeof source[key]) && !mergableTypes.includes(typeof target[key])){            if(key !== '__proto__'){                safeDeepMerge(target[key], source[key]);            }        }else{            target[key] = source[key];        }    }}
const displayWidgets = async () => {    const userWidgets = await (await fetch('/panel/widgets', {method: 'post', credentials: 'same-origin'})).json();    let toDisplayWidgets = {'welcome back to build a panel!': {'type': 'welcome'}};
    safeDeepMerge(toDisplayWidgets, userWidgets);
    ...};```
We can bypass the `__proto__` check in `safeDeepMerge` by using`constructor.prototype` instead, which is the same thing.
Some googling brings up a[related exploit](https://github.com/BlackFan/client-side-prototype-pollution/blob/master/gadgets/embedly.md)on [embedly](https://embed.ly/), the service used to show the reddit card at thebottom of the page. The exploit allows us to inject any attribute to the`iframe` of the reddit card.
The linked exploit uses `onload="alert(1)"`, but that didn't work for thischallenge due to the Content Security Policy:- `default-src 'none';`- `script-src 'self' http://cdn.embedly.com/;`  - Prevents inline JavaScript from executing- `style-src 'self' http://cdn.embedly.com/;`- `connect-src 'self' https://www.reddit.com/comments/;`
We read through embedly's `platform.js` script for variables to pollute andmanaged to discover some interesting tricks, but failed to find anything thatcould make the desired SQL injection request. After being stuck for hours, wewere ready to give up.
But in the last 30 minutes of the CTF, ath0 finally found a way to do it:
We knew we needed a way to make a GET request to the sql injection URL... but we don't need (and probably can't get) code execution. For a while we had looked for ways to hijack the URL of an ajax request (since the connect-src policy allows 'self'), but didn't find anything.
Since we just need to make the GET request and we don't really care what happens after, we could ask it to download a script or style (allows because script-src and style-src have 'self') from the SQL injection URL. So we looked for ways to insert a <link> tag.
![css-js.png](css-js.png)
This is interesting, it looked like it checks if the css attribute is set on some object... if it is, it loads a stylesheet by taking that attribute as the URL! Since our prototype pollution affects all `object`s... we can just try:
```pythondata = {"prototype": {"css": sql_url()}}```Since the css attribute is not otherwise set on this.data.options, our prototype pollution works and this.data.options has a css attribute containing our sql url.
Now all we have to do is run [pollute.py](pollute.py) and send the admin bot alink to our panel: https://build-a-better-panel.dicec.tf/create?debugid=yoink5
Visting the panel ourselves, we can see the flag added to our widgets:![flag.png](flag.png)
Thanks DiceCTF for the mind-bending challenge :)