type
            , reverse_iter_fold_null_step< Last,State >
            , reverse_iter_fold_step< First,Last,State,BackwardOp,ForwardOp >
            >::type res_;

        typedef typename res_::state state;
        typedef typename res_::iterator iterator;
    };
};

template<
      typename First
    , typename Last
    , typename State
    , typename BackwardOp
    , typename ForwardOp
    >
struct reverse_iter_fold_step
{
    typedef reverse_iter_fold_chunk< -1 >::template result_<
          typename mpl::next<First>::type
        , Last
        , typename apply2< ForwardOp,State,First >::type
        , BackwardOp
        , ForwardOp
        > nested_step;

    typedef typename apply2<
          BackwardOp
        , typename nested_step::state
        , First
        >::type state;

    typedef typename nested_step::iterator iterator;
};

template<
      long N
    , typename First
    , typename Last
    , typename State
    , typename BackwardOp
    , typename ForwardOp
    >
struct reverse_iter_fold_impl
    : reverse_iter_fold_chunk<N>
        ::template result_< First,Last,State,BackwardOp,ForwardOp >
{
};

}}}


Subdomain take over (xxx.xxxxxxxxxxxx.xxx)



Hi,


## Description

You have a subdomain aka `xxx.xxxxxxxxxxxx.xxx` that point to a third party service hosted on XXX: `www.XXX.com`. The nslookup command shows the DNS configuration.

```
$ nslookup xxx.xxxxxxxxxxxx.xxx 8.8.8.8
```

However it seems that your didn't own/claim the name `YYY` on XXX. That means an attacker could take it and trick your users/staff by copying your primary website and design.


## PoC

{}


## Risk

- fake website
- malicious code injection
- users tricking
- company impersonation

This issue can have really huge impact on the companies reputation someone could post malicious content on the compromised site and then your users will think it's official but it's not.


## Remediation

Remove the cname entry or claim the subdomain `YYY` on XXX.


## See also

https://labs.detectify.com/2014/10/21/hostile-subdomain-takeo