Public cloud storage meaning, in plain words

Public cloud storage misconfiguration leaves stored data open to anyone. What CWE-732 and OWASP say about reading and rewriting, and how to stop public access.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

A public cloud storage misconfiguration is a state in which the data in a cloud store can be seen by anyone. A store that holds contracts, customer lists, or backup files can have its public range set. If that range is widened too far, anyone who learns the URL can read it.

How does a public storage misconfiguration work?

It is like carelessly hanging a "help yourself" sign on the door of an in-house records room and forgetting to lock it. Nothing about the contents of the room has changed. Only the sign saying anyone may enter has. In a cloud store, one of the settings on the screen is that sign.

MITRE's CWE-732 deals with the weakness of permissions on important resources being assigned too loosely, and says it often occurs in the cloud. If a store or a place where files are kept is open to public or anonymous access, outside people can read or rewrite its contents.

CWE-732 also lists possible effects: credentials and configuration files going outside, permissions being taken through rewritten executables, and data being destroyed or deleted. The point is that it is not a problem of being read only.

The 2021 edition of the OWASP Top 10 gives wrong cloud permission settings as an example of security misconfiguration. It is the scene where a provider's default sharing settings stay open to other users on the internet and reach the data in a store. Its countermeasures include reviewing store permissions, such as S3 bucket permissions.

How to find and fix it is set out in public cloud storage misconfiguration. The free URL check reads only from the outside and cannot list what is stored in your storage service.

Why does a public storage misconfiguration matter?

It is a problem that is easy to notice late, because nothing looks wrong on the screen. Even if customers' files can be seen from outside, the site goes on working as usual. If personal information is included, the fact that even one record could be seen harms trust. To talk through what to do, contact us.

The basic fix is to stop the public access. CWE-732 lists disabling public access in the provider's admin screen and removing broad targets such as everyone or all authenticated users from the permissions. After stopping it, check whether it had been seen from outside before you changed the setting.

It helps the investigation if you can trace who changed the setting and when it became public. The explanation of IAM is a guide to how permissions are held. The problem of the keys for entering a store getting out is covered in access key leaks.

Related terms

  • Cloud misconfiguration: a state in which wrong public-range or permission settings become a hole
  • IAM: the mechanism that decides who may do what in the cloud
  • Access key leak: keys that operate the cloud getting out
  • CSPM: a mechanism that finds cloud misconfigurations automatically

Frequently asked questions

Can a public-setting mistake also let data be rewritten?

Yes. CWE-732 explains that if storage is open to public or anonymous access, outside people can not only read its contents but also rewrite them. It also lists, among the effects, gaining permissions when executables are rewritten and destruction of data.

What should I do first when I notice a public-setting mistake?

Stop the public access. CWE-732 gives as examples disabling public access in the provider's admin screen and removing broad targets such as everyone or all authenticated users from the access permissions. After that, check whether it had already been viewed from outside.

Next step

List your stores in the admin screen and check whether any allow public access. The whole of preparation against information leaks is in information leak countermeasures, and a concrete check is in public cloud storage misconfiguration. The free URL check sees only the outside of your site, and for a review of how your stores are configured, contact us.

Frequently asked questions

Can a public-setting mistake also let data be rewritten?

Yes. CWE-732 explains that if storage is open to public or anonymous access, outside people can not only read its contents but also rewrite them. It also lists, among the effects, gaining permissions when executables are rewritten and destruction of data.

What should I do first when I notice a public-setting mistake?

Stop the public access. CWE-732 gives as examples disabling public access in the provider's admin screen and removing broad targets such as everyone or all authenticated users from the access permissions. After that, check whether it had already been viewed from outside.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.