Answer is simple:
No there isn't.
According to the RFC only one wildcard is supported:
Matching is performed using the matching rules specified by
[RFC2459]. If more than one identity of a given type is present in
the certificate (e.g., more than one dNSName name, a match in any one
of the set is considered acceptable.) Names may contain the wildcard
character * which is considered to match any single domain name
component or component fragment. E.g., .a.com matches foo.a.com but
not bar.foo.a.com. f.com matches foo.com but not bar.com.
However what you can do is to get a wildcard certificate for *.apps.domain.com which will cover every sub domain of apps.domain.com and another one for *.domain.com to cover the first level subdomains.
Taken from: https://www.instantssl.com/articles/can-you-create-a-wildcard-ssl-certificate-for-two-levels.php:
The reasons it is not possible to have a "double wildcard" SSL
certificate is that the placeholder, the asterisk, can only stand in
for one field in the name submitted to the CA. After all, the CA has
to verify all information, and too many variables in the certificate
would decrease the security and confidence the certificate provides.
Additionally, and this is important for IT managers and website owners
as well, the internal security cannot be compromised as easily. Keep
in mind that any type of security issue once an SSL certificate is in
place is much more likely to occur from an internal security breach
where someone with access to the private key and certificate is able
to set up a subdomain website that is actually covered by the SSL.