Skip to content

Commit 733e3b1

Browse files
Merge branch 'main' of github.com:Innoptech/OpenSTL
2 parents 48b368c + 588e61c commit 733e3b1

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -149,9 +149,11 @@ quad[:,1:4,:] *= scale # Avoid scaling normals
149149
```
150150

151151
### Read large STL file
152-
To read large STL file with a large triangle count > **1 000 000**, the openstl buffer overflow safety must be unactivated with
152+
To read STL file with a large triangle count > **1 000 000**, the openstl buffer overflow safety must be unactivated with
153153
`openstl.set_activate_overflow_safety(False)` after import. Deactivating overflow safety may expose the application
154-
to potential buffer overflow risks (if openstl is used in a backend server with sensible data for example).
154+
to a potential buffer overflow attack vector since the stl standard is not backed by a checksum.
155+
This can cause significant risks if openstl (and any other STL reader) is used as part of a service in a backend server for example. For
156+
domestic usage, ignore this warning. OpenSTl is the only stl reader to provide such default safety feature.
155157

156158
# C++ Usage
157159
### Read STL from file
@@ -261,4 +263,4 @@ The STL file format, while widely used for 3D modeling and printing, was designe
261263

262264
- Potential for Buffer Overflow Attacks: The lack of built-in validation and the absence of bounds checking in the STL format can make it susceptible to buffer overflow attacks. Care should be taken when handling STL files, especially those from untrusted sources, to ensure they are properly validated before being used.
263265

264-
These limitations are inherent to the STL format and should be considered when working with or implementing software that processes STL files. Developers are encouraged to implement additional validation and error-handling mechanisms in their applications to mitigate these risks.
266+
These limitations are inherent to the STL format and should be considered when working with or implementing software that processes STL files. Developers are encouraged to implement additional validation and error-handling mechanisms in their applications to mitigate these risks.

0 commit comments

Comments
 (0)