I checked BSD, GNU GPL and Creative Commons. They all allow the redistribution with giving the credit. I, however, don't want people to redistribute my product, but only use it. Is there a license for that?
Commercial software licenses are generally written by a lawyer working for the publisher.
There are no ready-made texts you can just apply to your work, for several reasons, the most prominent of them being that lawyers are neither permitted nor interested in working for people who aren't their clients, and they are especially not interested in litigating a case around a license statement that someone else wrote, and where it is unclear what qualifications the person writing the license had.
The GPL was initially used only by the GNU project, and it was understood that contributors had to assign copyright to the project to give them standing to litigate against infringement. Laypeople using the license without copyright assignment is a later development, after there was sufficient case law.
So, you will need to hire a lawyer, preferable the same you will also hire when someone is in breach of your license.
A license which merely permits use will not permit distribution. The one exception is that in some jurisdictions if a person (or firm) transfers a lawfully acquired and licensed program to another, adn destroyies any instances noty transferred, the recipient may lawfully use the program under the original license and subject to its terms.
Permission to redistribute software, or any other work protected by copyright, must be specifically granted. In the absence if such permission (usually in the form of a license) making and distributing copies would be copyright infringement and could be the occasion of a civil suit for infringement.
Most open source and "free software" projects want users to distribute copies widely. So do so-called "shareware" projects. Licenses such as BSD, GNU, GPL, CC, MIT, and Apache (among others) are designed for projects where redistribution is desired, and are not suitable for commercial, closed-source software. Examine the license on several commercial consumer software packages. You will soon see common elements in many such license texts.
This list contains information about several books which describe in detail how to draft adn use software licenses, some in open-source situations, but some in close-source contexts. There are other similar books in print on this topic. These provide some alternatives to hiring a lawyer to draft a custom-license for a project, although getting actual legal advice may be wise at various steps of such a business venture.
I cannot specifically recommend any of these books, but I have used a somewhat similar book (now out of print and out of date) and found it satisfactorily for sideline published software ventures.