Back to bug 2137776
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| TEJ RATHI | 2022-10-26 07:36:53 UTC | Depends On | 2137778 | |
| TEJ RATHI | 2022-10-26 07:37:30 UTC | Blocks | 2137644 | |
| TEJ RATHI | 2022-10-26 07:42:04 UTC | CC | abokovoy, anoopcs, asn, dkarpele, gdeschner, jrivera, pfilipen, rhs-smb, sbose | |
| Kazu Yoshida | 2022-10-28 07:53:48 UTC | CC | kyoshida | |
| Sage McTaggart | 2022-10-28 20:52:59 UTC | Depends On | 2138446 | |
| TEJ RATHI | 2022-10-31 12:30:00 UTC | Doc Text | A symlink following issue was discovered in Samba, where a user can create a symbolic link that will make 'smbd' escape the configured share path. A remote user with access to the exported part of the file system under a share via SMB1 unix extensions or NFS can create symlinks to files outside of the 'smbd' configured share path and get access to other restricted server's filesystem. | |
| RaTasha Tillery-Smith | 2022-10-31 13:02:17 UTC | Doc Text | A symlink following issue was discovered in Samba, where a user can create a symbolic link that will make 'smbd' escape the configured share path. A remote user with access to the exported part of the file system under a share via SMB1 unix extensions or NFS can create symlinks to files outside of the 'smbd' configured share path and get access to other restricted server's filesystem. | A symlink following vulnerability was found in Samba, where a user can create a symbolic link that will make 'smbd' escape the configured share path. This flaw allows a remote user with access to the exported part of the file system under a share via SMB1 unix extensions or NFS to create symlinks to files outside the 'smbd' configured share path and gain access to another restricted server's filesystem. |
| Red Hat Bugzilla | 2023-01-01 08:30:14 UTC | CC | gdeschner | |
| Alasdair Kergon | 2023-01-04 04:54:53 UTC | CC | gdeschner | |
| Red Hat Bugzilla | 2023-01-16 08:27:30 UTC | CC | jrivera | |
| Red Hat Bugzilla | 2023-07-07 08:29:25 UTC | Assignee | security-response-team | nobody |
Back to bug 2137776